Android M Developer Preview - Nexus 9 General

It's here! Downloading it now and I'll flash it ASAP. Download link here, for those who want to give it a try:
http://developer.android.com/preview/download.html
I'm also gonna throw it out there: if you don't know how to flash this image you probably shouldn't. This is a developer preview and you are likely to run into far more problems than you would with the current official release.

I don't think it works with Nexus 9 LTE though
Edit: So you can flash the system, boot, cache and vendor img files using fastboot and get it working with just wifi. Just tried and successfully booted.

shenye said:
I don't think it works with Nexus 9 LTE though
Click to expand...
Click to collapse
no, probably not. it'll be no different from trying to flash the normal nexus 9 image with the LTE model. that image probably won't come out until the final release - this is just a developer preview after all.

Flashed (did a dirty flash, without performing a factory reset), but back to 5.1.1 now. At least in my case I found it impossible to use as a daily driver.
Issues discovered:
1. Settings panel (in notifications) had an extra white pane underneath. Once swiped away / clicked, the settings panel was not available anymore when dragging down from the notification area.
2. Home button not working
3. Unlock screen missing, on wake up the desktop is displayed, however swiping occasionally produces an unlock effect.
4. Facebook app crashes when trying to open it.
5. Holding and swiping up on the home button did nothing (instead of opening Google Now)
Other discoveries:
1. The application drawer now scrolls vertically. It has a search bar and the last apps (or maybe most used?) at the top, separated by a horizontal line from the rest of the drawer. When scrolling, only the search bar remains pinned at the top.
2. Profile icons on the right side, (only) the first time the notification panel is pulled down.
3. The notification panel opens wherever you swipe your finger from the top (not centered anymore).
4. The volume pane now has a drop down button on the right that reveals the other volume channels.
Warning: for me flashing back (again dirty flash) to 5.1.1 leads to a boot loop, where it boots, optimizes the apps, then throws a short Google Play Services has stopped and then black screen and reboots. Then does it again.

adancau said:
Flashed (did a dirty flash, without performing a factory reset),
Click to expand...
Click to collapse
I have no clue why you would do that then complain about what doesn't work.

JeeperDon said:
I have no clue why you would do that then complain about what doesn't work.
Click to expand...
Click to collapse
I was not complaining (I take full responsibility for flashing a preview edition). I was just describing my experience.

JeeperDon said:
I have no clue why you would do that then complain about what doesn't work.
Click to expand...
Click to collapse
So, to do this properly, do I have to unroot and go back to stock recovery? Or what's the best process when I'm unlocked, rooted, and with customer recovery already?

generosity21 said:
So, to do this properly, do I have to unroot and go back to stock recovery? Or what's the best process when I'm unlocked, rooted, and with customer recovery already?
Click to expand...
Click to collapse
You don't have to unroot and go back to stock (as this is not an update). If you go into the bootloader (adb reboot bootloader) and flash all the img files in the factory image (fastboot flash * *.img, where * is bootloader, boot, system, cache etc.) it will give you stock Android M. I'm saying flash the img files, as for me the flash-all thing didn't work (it complained about the system partition, apparently a common issue).

adancau said:
You don't have to unroot and go back to stock (as this is not an update). If you go into the bootloader (adb reboot bootloader) and flash all the img files in the factory image (fastboot flash * *.img, where * is bootloader, boot, system, cache etc.) it will give you stock Android M. I'm saying flash the img files, as for me the flash-all thing didn't work (it complained about the system partition, apparently a common issue).
Click to expand...
Click to collapse
Thanks! Can I skip the recovery.img and keep my custom recovery, or is that likely to cause problems?

generosity21 said:
Thanks! Can I skip the recovery.img and keep my custom recovery, or is that likely to cause problems?
Click to expand...
Click to collapse
I wouldn't. But you could experiment I guess (no guarantees though). Before you proceed make sure OEM unlocking is still on in Developer options, just in case.

Can someone who flashed it say some words about the the first impressions regarding performance ?

so after over an hour of trying to get it to work, i've finally got it to boot into the OS. i ended up having to force reboot it a bunch of times during the initial loading animation. interestingly, it showed a small warning for 5 seconds saying something like "your device has failed verification and may not work properly" with a red warning symbol on top, right after the bootloader splash screen.
before i force reset it (and reflashed the system image twice) it would get stuck at the loading screen for a very long time, much longer than what is normal for an initial boot on an encrypted device, and the top right corner of the tablet was getting very warm, meaning it was clearly working on something - maybe stuck in an infinite loop? anyway, installing my applications from a backup now and i'll get back about the performance and how it works.
something interesting i noticed right away is that when swiping down to show the notification shade, instead of always coming down right in the center it'll slide out from either the left, right or center of the status bar depending on where you swiped down. cool trick for making one-handed use easier i guess. i'll see if i can take a few screenshots once everything's set up.
oh, something else - there are a bunch of new neat animations everywhere. everything's a bit more fluid and there are some nice touches in a few places. not really something that can be explained without experiencing it though.
aside from the issues with booting up i haven't run into any other problems yet.

Flashed manually partition by partition, and erased user data before booting.
Absolutely no issues during flash and it booted on the first attempt.
It's currently restoring from my last Google backup, but so far a pretty easy experience (beyond flash-all being broken).

ooh there are a bunch of new battery optimization and battery usage tracking features, as well as a utility which tracks memory usage of various apps, and how often an app is running - and lets you choose whether to look at the past 3 hours, 6 hours, 12 hours and day.

foxmeister said:
Flashed manually partition by partition, and erased user data before booting.
Absolutely no issues during flash and it booted on the first attempt.
It's currently restoring from my last Google backup, but so far a pretty easy experience (beyond flash-all being broken).
Click to expand...
Click to collapse
I've noticed that the audio doesn't keep up with the keyboard if you type in any way reasonably quickly. Definitely seems slower to me so far compared with 5.1.1. I did a full clean wipe. I'm gonna do a restart once i install some stuff again and see if it clears it up. Noticed that the theme option under 'developer options' has an 'automatic' option, itd be pretty cool if it turned on at night for instance but its 10:24pm here in N.Ireland and it didnt go to dark mode when i chose automatic so who knows. Also see an option to enable/disable tap-to-wake, not something I want to disable but handy enough for those who do and maybe even potentially a small battery saving.
Jumpy audio through google play music, presumably related to the keyboard issue I was talking about. Still haven't restarted yet though.
EDIT: dark theme has enabled itself after i set the theme option to 'automatic', presumably because it's night time

seanashmore said:
I've noticed that the audio doesn't keep up with the keyboard if you type in any way reasonably quickly. Definitely seems slower to me so far compared with 5.1.1. I did a full clean wipe. I'm gonna do a restart once i install some stuff again and see if it clears it up. Noticed that the theme option under 'developer options' has an 'automatic' option, itd be pretty cool if it turned on at night for instance but its 10:24pm here in N.Ireland and it didnt go to dark mode when i chose automatic so who knows. Also see an option to enable/disable tap-to-wake, not something I want to disable but handy enough for those who do and maybe even potentially a small battery saving.
Jumpy audio through google play music, presumably related to the keyboard issue I was talking about. Still haven't restarted yet though.
Click to expand...
Click to collapse
Oddly, mine did go dark when I set the theme to automatic - I'm in England, so same time zone as you.
Can't say much else yet - still downloading my apps.
Quite a few force close pretty much immediately when I try to run them, but I'll let the restore take its course and reboot before making any firm judgements.
Given how generally poor my experience with my N9 has been to date, I'm prepared to put up with a few warts and teething issues.

adancau said:
I was not complaining (I take full responsibility for flashing a preview edition). I was just describing my experience.
Click to expand...
Click to collapse
I dont think its the fact that its dev preview that messed you up. By dirty flashing and then claiming it is not stable enough for a DD is stupid tho. If you want to truly experience it and not going around telling people you cant use it, then you should probably clean flash.

addicted1900 said:
Can someone who flashed it say some words about the the first impressions regarding performance ?
Click to expand...
Click to collapse
Its running great so far. Seem smooth for a dev preview. No FCs or other problems so far.

ilatimer1 said:
Its running great so far. Seem smooth for a dev preview. No FCs or other problems so far.
Click to expand...
Click to collapse
thanks. Then i will make the step tomorrow.

Does it still heats up like crazy when using Chrome?

Related

[Q] Bell - Any way to remove sys apps; add tomtom?

I just traded up from an HTC Legend to a Desire Z but unfortunately I have two gripes which are both due to Bell:
1) Preinstalled games and apps. Asphalt 5; Cyberon Voice; GPS Navigator; Kobo; Let's Golf!; Remote PVR; SoundHound; Tunes & Apps; TV & Radio; UNO; Zoompass. 11 apps that I don't need. 11!
2) HTC Locations is missing. Instead they want you to use GPS Navigator which is $10 a month. No thanks!
Anyway my questions are:
1) Is there any way to remove the excess apps without a full root? Ex: with VISIONary + another apps?
2) Is there any way to get HTC Locations back? I see it in some of the system settings, but can't actually launch it.
not too sure about htc places, but to remove those waste of space third party Apps all you need to do is run visionary. once you've done that, load up Root Explorer application and navigate to /system/app/ directory. here you will find those pesky Apps and games, but be careful with what you delete. some of these apk's are critical to htc sense. good luck... let me know how it turns out.
Sent from my HTC Desire Z using Tapatalk
Thanks for the reply but as with my Legend, it's all back after reboot. :-(
Sorry, I currently just experienced the same thing. I think this occurs due to the apk remaining in /data/Dalvik-cache/ files. I would suggest deleting the files corresponding to the .apks you remove and repeat the first process as well.
Sent from my HTC Desire Z
That seemed to have solve the problem. I just rebooted and they did not return. Let me know if it works for you.
Sent from my HTC Desire Z
No go. I deleted from /system/app and /data/dalvik-cache but after reboot, everything is back.
Maybe you did a power down and then turned it on again - since they have quick-boot now (aka sleep mode) it doesn't actually power down or restart the phone, causing it to appear as if the changes stuck when they didn't.
I remember reading that you need a true root to get rid of sys apps on HTC phones, but I also thought I saw something about doing it from command line on a PC somehow.
The practice of preloading uninstallable demos and useless apps is unacceptable.. ugh
have you checked the G2 forums ??
This same Q for this same device has been previously asked and discussed there
They are lightyears away form us
I still think both forums should be merged...
.
gtrab said:
have you checked the G2 forums ??
This same Q for this same device has been previously asked and discussed there
They are lightyears away form us
I still think both forums should be merged...
.
Click to expand...
Click to collapse
Agreed, it's going to be kinda silly have the two sets of forums. On the G2 they've figured out loads of things like this already.
The new HTC phones have a good system protection thing going on.
Basically each time you reboot the phone it checks to see if the contents of /system has been edited (apps added or removed etc etc) then if it has changed it will reflash it back to stock.
Basically you can root using "visionary" and make any changes you want, but as soon as you reboot it will all change back.
That being said Modaco has now come up with a method for removing apps permanently but not adding them.
Lennyuk said:
The new HTC phones have a good system protection thing going on.
Basically each time you reboot the phone it checks to see if the contents of /system has been edited (apps added or removed etc etc) then if it has changed it will reflash it back to stock.
Basically you can root using "visionary" and make any changes you want, but as soon as you reboot it will all change back.
Click to expand...
Click to collapse
That was the original story, but I think it's been debunked now, hasn't it ? It doesn't revert things to normal once you reboot (as proved by Paul's program which can delete built-in apps), but merely prevents you from writing to the on-board storage.
steviewevie said:
That was the original story, but I think it's been debunked now, hasn't it ? It doesn't revert things to normal once you reboot (as proved by Paul's program which can delete built-in apps), but merely prevents you from writing to the on-board storage.
Click to expand...
Click to collapse
not quite
Pauls method basically tricks the phone into thinking the app was legitimately removed therefore it doesn't think there is an issue so won't reflash it.
Lennyuk said:
not quite
Pauls method basically tricks the phone into thinking the app was legitimately removed therefore it doesn't think there is an issue so won't reflash it.
Click to expand...
Click to collapse
I don't think that's right though. Paul's method just fools the phone into deleting the app as part of a supposed update.
There is no check to see if anything's been changed when the phone boots, as far as I can tell from the G2 forums.
steviewevie said:
I don't think that's right though. Paul's method just fools the phone into deleting the app as part of a supposed update.
There is no check to see if anything's been changed when the phone boots, as far as I can tell from the G2 forums.
Click to expand...
Click to collapse
Well it has to check something otherwise it would not know to erase anything you change like Overclock levels etc.....
Lennyuk said:
Well it has to check something otherwise it would not know to erase anything you change like Overclock levels etc.....
Click to expand...
Click to collapse
It doesn't erase those though, it's just that when you "change" them via the tools, it doesn't write to the internal storage, it's just caching the changes in RAM. So it reads the cache and uses the changes. When you reboot, of course the cache is flushed, so the changes disappear.
They used to think there was a "revert to stock on reboot" thing on the G2 too, a few weeks back. No disrespect, but this is an example of how out of date "we" are here on the DZ forums, compared to the G2 which has been out a few weeks now.
steviewevie said:
It doesn't erase those though, it's just that when you "change" them via the tools, it doesn't write to the internal storage, it's just caching the changes in RAM. So it reads the cache and uses the changes. When you reboot, of course the cache is flushed, so the changes disappear.
They used to think there was a "revert to stock on reboot" thing on the G2 too, a few weeks back. No disrespect, but this is an example of how out of date "we" are here on the DZ forums, compared to the G2 which has been out a few weeks now.
Click to expand...
Click to collapse
hmm, I am still not convinced caching would hold it without significantly lowering perfomance, plus why the very very long boot times when you do make a change and then reboot?
Lennyuk said:
hmm, I am still not convinced caching would hold it without significantly lowering perfomance, plus why the very very long boot times when you do make a change and then reboot?
Click to expand...
Click to collapse
Try asking about this on the G2 forum if you like ...
On the caching thing, there's more in the Wiki - http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Intro . Specifically :
For anyone interested-- despite what the blogs are saying-- THERE IS NO "ROOTKIT" and THERE IS NO "RESTORE ON REBOOT". What *is* happening is that Android thinks it's writing to the eMMC (memory card), but it is not. What you are seeing as a successful write is just the cache
Click to expand...
Click to collapse
And here's the proof - http://pastebin.com/cm75Z9UA
Lennyuk said:
hmm, I am still not convinced caching would hold it without significantly lowering perfomance, plus why the very very long boot times when you do make a change and then reboot?
Click to expand...
Click to collapse
Because that's a REAL reboot
The fabulous fake "5 seconds boot time" is just a hibernation trick, a feature called "HTC Fast Boot" (= power off hybernates instead of really "powering off").
Check the G2 forums, this has been confirmed by HTC.
When you press "power off", the phone DOESN'T power off, it just "hibernates", then when you power the phone on again, you see the "amazing 5 seconds boot up"
If you want REAL power off you have to REMOVE THE BATTERY
.
gtrab said:
Because that's a REAL reboot
The fabulous fake "5 seconds boot time" is just a hibernation trick, a feature called "HTC Fast Boot" (= power off hybernates instead of really "powering off").
Check the G2 forums, this has been confirmed by HTC.
When you press "power off", the phone DOESN'T power off, it just "hibernates", then when you power the phone on again, you see the "amazing 5 seconds boot up"
If you want REAL power off you have to REMOVE THE BATTERY
.
Click to expand...
Click to collapse
So how long are these very very long boot times??? Have had android 2.1 take about 1 minute to load up normally on a 600mhz processor, so surely 2.2 wouldn't take much longer than this?! ???
Anyway, back to the question (in a way)...
Is TomTom actually available as standard on the Desire Z? As I'm sure I read somewhere that it was Route66 or some other software with a similar name, not TomTom...
gtrab said:
Because that's a REAL reboot
The fabulous fake "5 seconds boot time" is just a hibernation trick, a feature called "HTC Fast Boot" (= power off hybernates instead of really "powering off").
Check the G2 forums, this has been confirmed by HTC.
When you press "power off", the phone DOESN'T power off, it just "hibernates", then when you power the phone on again, you see the "amazing 5 seconds boot up"
If you want REAL power off you have to REMOVE THE BATTERY
.
Click to expand...
Click to collapse
yes thanks but I knew this already, I knew this from the moment I heard of the new "fast boot" its the same as blackberry have been using for years

Blackhole 4.x to SuperClean 2.x observations

Awesome ROM - thanks for sharing your work!
I flashed the standalone 4.0 followed by the 4.01 update. Now I'm grabbing extras a bit at a time. Some observations/questions:
1. When I boot/reboot, I let the phone settle in (read SD,etc). I unlock, but then Launcher Pro is completely unresponsive. I must long press home button & use task mgr to kill it. When it comes back, all is good until next reboot.
2. I restored downloaded apps using Titanium. Market is not recognizing any as installed. First time I've gone this route. Expected?
3. I can't back out of Contacts; gotta use Home button.
4. Recently edited Memos don't come to the top of the list. Can that be reverted to the 2.1 behavior?
Small stuff in view of super clean, super cool ROM.
Thanks again!
It's disappointing, but I feel certain this post would have gotten a reply or some comments if posted in the Dev section. Here in the General section, it's either remained below the radar or been ignored. Can a mod or admin tell me if there was a more appropriate place for my post? Obviously, I haven't met the 10 post minimum, or I would have popped it in the Dev section in the Blackhole thread where others are posting their observations and feedback of that ROM. Thanks.
upgrade to Blackhole 4.2
Might as well work my way towards the 10-post minimum so I can post to the dev section where discussion actually happens...
I followed this thread to get CWM shaped up:
http://forum.xda-developers.com/showthread.php?t=957132
Trying a backup initiated through ROM Manager resulted in badness, so I repeated the steps for CWM (using Odin). BTW, I had to boot the phone once without the SD card to move past being stuck at the Samsung logo. I then rebooted into CWM (red) and did a backup.
Then I followed SoS's instructions and installed the standalone 4.2:
http://forum.xda-developers.com/showthread.php?t=940456
As long as I was just working within CWM, I was fine. ROM Manager is totally hosed. It really can only be used now to browse the ala carte options. Trying to install through it results in being stuck at the Samsung logo. 3-fingered booting from powered off doesn't even work. Repeat the CWM fix (using Odin) and boot once without the SD card.
To get around ROM Manager Madness, I use it to pick the options I want, then cancel the final step, reboot into recovery from a long press of the power button and use CWM to install the individual zips. Fine.
The original oddities in Blackhole 4.x are still present on my device. The two that are most bothersome: [1] I can't back out of contacts [2] Launcher Pro is unresponsive after booting.
For the contacts issue, create a new link to contacts from the app drawer and use the new one to replace the existing.
good day.
chopper the dog said:
For the contacts issue, create a new link to contacts from the app drawer and use the new one to replace the existing.
good day.
Click to expand...
Click to collapse
Thanks for the reply, I'll try that.
Worked great, thanks!
clock lag persists
Initially I thought that the clock lag I was experiencing in 4.01 was gone in 4.2. Nope, it remains. As others have said, seems to be related to enabling Wi-fi.
I'll go check the threads for updates but, last I checked, a double reboot was the suggested fix. I'm not clear whether people were suggesting that to be some sort of permanent fix. It didn't seem to be for me.
The time would correct after the first reboot and I would reboot again to comply with the posts, but I <think> the problem would return under 4.01. Now under 4.2, I'm sure. Last night, I double-rebooted and this morning the clock was 20 minutes slow.
Like I said, I'll go looking for updates now. Could be that this has already been resolved for real.
voice recorder, car home
Just adding a couple more oddities to the current list: voice recorder force closes and car home doesn't come up automatically when you plug in to the car cradle.
Reloading the voice recorder zip through CWM was about the only tactic I tried with no luck. Then I wanted to grab something for the ROM over-the-air, but the site was down. Checked in here and saw there was a problem with the host. That interruption of being able to download pieces parts OTA was kind of the proverbial straw, so I'm trying a SuperClean.
Pushed it through Odin and the process was smooth. The ROM looks good. None of the same oddities except the clock lag. I'm changing the sleep state of Wi-fi to see if that makes a difference.
SonofSkywalker does amazing work and I'm sure I'll be trying his ROMs again. For now, though, something different.
clock lag fix?
as per a forum suggestion, I changed the Wi-fi sleep setting. So far, it seems to prevent clock lag.
Home Screen | Menu | Settings | Wireless & Network | Wi-Fi settings | Advanced | Wi-Fi sleep policy -> select 'When screen turns off'.
Does anyone know if this has been an issue in the VZW full stock 2.2?
battery life is better
Under Super Clean 2.6, launching Google Maps and exiting has released the wake lock and battery life is much better.
Does a user guide, sticky or FAQ exist for Spare Parts? I could see that "other | running" was 100%, but I wasn't sure how to zero in on what was causing it other than trial and error based on other users' posts.
unread email count
A quick search of the forums didn't turn up much discussion, so I'll throw this out there:
on DL30 leak, the general email icon would increment and not decrement or clear until mail was manipulated on the phone. In other words, if it said 3 unread messages and I used Outlook (or the mail provider's web mail) to deal with them, it would sync and accurately display the message state in the list of emails - but the email icon on the home screen would still show 3. If 3 more came in and again they were dealt with elsewhere, the icon would go to 6. Only if action was taken on the phone itself would the counter "get real".
On Blackhole 4.x and SuperClean 2.x (any custom EB01 ROM?), the email icon on the home screen doesn't show an unread count (fine by me, I don't miss it), but when you pull down the notification bar, the unread count there acts exactly the same way.
Anyone else experiencing this? Devs, can it be fixed?
Did you clear your cache and davlik? I had some issues(when I closed an app none of my apps would show up and overall everything was running really slow). However when I was on superclean 2.6 I cleared my cache and davlik(for the first time) before I upgraded to superclean 2.8 and overall everything is working no problems.
thanks i havent used anything but sc!

Westcrips v8.4 Ressurection -> Discussion

Post updated to reflect current version.
OK.. I'm mainly posting this here because my PC is too low to post in the dev thread.. and I think its best to leave that thread to dev discussion...
First impressions:
Installs quite smoothly and pretty fast.
My install method (in case its needed later)
- Back up and copy to pc
- Complete wipe to stock gb. Root gb and install cwm
- Copy ressurection 8.1 zip to SD card
- Reboot to cwm
- Format data/cache, dalvic cache, system and battery stats
- Reboot to cwm
- Select resurrection 8.1 zip and install. Takes about 5 min
- Reboot to recovery and factory reset (probably not needed but did it to be safe)
- Reboot normally and let system boot up. Takes 3-5 min on first boot
Now on to the fun stuff... on first boot I set up language, clock wifi account etc.
I selected and only use nova... I like it better than trebuchet.
Gmail notification crashes Google accounts right off the bat. This is persistent throughout 3 installs. Seems to work fine after initial crash.
Once SD card scanning and such finishes, i disable fast dormancy (*#*#9900#*#* for menu) thenI reboot normally.
Open market, works fine.. install some primary apps... titanium backup & pro key.. better battery stats, root explorer and LCD density monitor pro.
Set dpi to 160 to give me better screen real estate.. then reboot normally
I'm about 11.5 hours on battery and 83% battery with light to moderate use.. I disable mobile data stuff unless I need it, and generally keep wifi active most of the time..
Overall most things run very smoothly. Some apps don't seem to close properly when killed but I assume its due to those apps.
System does get laggy if a lot of apps are open and sleeping.. I use ATK pretty often to keep things smooth...
Problems I've run in to so far...
This one is pretty big I think... when using flashlight from notification panel, if I leave it on until it times out, my phone completely freezes and I have to long power press to reboot or remove battery to get system rebooted. This is persistent and replicated every time I tried.
Gmail app crashes about 30% of the time. Seems completely random. I'v disabled Gmail notification due to this.. (doesn't crash google accounts like above, just the gmail app)
When holding phone I can feel a very very faint vibration coming from the back side up near the camera.. it pulses about once every 2 seconds. You have to very lightly touch the phone to feel it.. like barely touching it. Not sure if its just mine but its very noticeable if you hold it right. Not sure what's causing this.. doesn't seem to affect anything and phone isn't overheating so I can't give more info...
Random reboots are something everyone is aware of so not commenting there. Nova does hang sometimes for 5-10 seconds. Probably due to this being a dev release and such things are expected.
I'll update more if/when I run in to other issues that people haven't really commented on...
Sent from my GT-I9100 using xda premium
android.acore process keep FC..really disturbing..
it bcoz of auto sync and i hope someone have a fix on this
I think v8.2 is the best among Westcripts ROMs. because of the least FC.
V.8.3
Flashed since yesterday , very stable , no FC's at all, however there is an USB problem , PC won't recognise the devised the way it was in previous versions. Nevertheless I believe it's a ICS bug as I found same behaviour in other Roms as well.
Not bad so far using 8.3
I noticed in his dev post he said that official ICS doesn't have blue coloured wifi/signal bars but I've used my friends nexus & his definitely has blue coloured wifi/signal bars when in use.
Everything else seems pretty smooth at the moment.
Looks like this problem with blue bars has been resolved in 8.4 Currently downloading (check change log).
Not being funny, but is there not a thread in the Development section to discuss this rom, surely creating another, just fragments the chefs build
THUDUK said:
Not being funny, but is there not a thread in the Development section to discuss this rom, surely creating another, just fragments the chefs build
Click to expand...
Click to collapse
Would have posted my thoughts there but I don't really want to spam 10 posts just to be able to :/
Downloading/Installing 8.4 now
SMe too.. I have flashed the new version and it seems fine. I haven't checked the GPS yet. What I want from this rom is
T9 dialer in aosp theme
Full screen call id like aosp
Aosp boot
THUDUK said:
Not being funny, but is there not a thread in the Development section to discuss this rom, surely creating another, just fragments the chefs build
Click to expand...
Click to collapse
Well actually, that thread is supposed to be for development discussion only; not for general Q&A 'how do I do this or that' like it has been. Which means, if people actually adhered to the rules, using this thread for all the 'HALP' posts would likely make development a lot easier for those working on this particular project. The less spam he has to sift through, the more actual development related posts he can focus on.
Not to mention, as I stated in the OP of this thread, I wasn't able to post my bugs there because of my post count.. So i posted them here, along with some other info (like how to install) about the release.
If only everyone who tried to play forum police actually knew what the dev forums are supposed to be for........
no searching for contact when I typing in number in phone, and T9 is not working in v8.4
Do any of u have the issue with notifications having a 'grey background'? I've had this since 8.3.
Also how can I change back to the stock bootanimation?
Thanks.
cpark85 said:
Do any of u have the issue with notifications having a 'grey background'? I've had this since 8.3.
Also how can I change back to the stock bootanimation?
Thanks.
Click to expand...
Click to collapse
I used a app called ROM toolbox suggested in the dev thread to change the bootanimation to the ICS one.
Notifications come up grey here on 8.4.
cpark85 said:
Do any of u have the issue with notifications having a 'grey background'? I've had this since 8.3.
Also how can I change back to the stock bootanimation?
Thanks.
Click to expand...
Click to collapse
No issue with the notifications that I've seen so far on 8.4
To get the Samsung boot animation back, do the following:
if you have 8.3 or an earlier version, extract a copy then navigate to extracted file > system > media
copy bootsamsung.qmg and bootsamsungloop.qmg to your sd card
in root explorer, navigate to your sd card > hit menu and multi select. Select the above to files then click copy/move.
Navigate to /system/media > mount R/W > paste.
Remove bootanimation.zip
set back to R/O and reboot phone.
chanrocky said:
no searching for contact when I typing in number in phone, and T9 is not working in v8.4
Click to expand...
Click to collapse
Temporary fix posted by kevjef420:
go to market and install these three apps. ex dialer, ex dialer ics theme and ics adw theme by kovdev.
set the ex dialer as your main dialer in dock. open setting for ex dialer and select ics theme. then long click on the ex dialer icon in your dock and click edit and select adw theme pack and then find the ics blue phone icon.
now you have a very functional t9 dialer that is very similar to the miui dialer and it works great. I am very happy with the results. this is a good fix untill somebody comes up with a t9 fix for asop dialer.
I've flashed 8.5 and set language to German but somehow it's a mix of German and English!?!
Anybody with same problem or similar?
Navigation from Google Maps keeps force closing everytime i have GPS signal. Maps works fine. What could it be?
Thanks in advance!
v. 8.6
Just installed 8.6, really fast and smooth. Hour in use, no more process stopped.
I am not sure why but in one app's browser and in stock Android file browser I get unusual wide slider. It was normal on 8.4, but changed on 8.5.
xitake said:
Navigation from Google Maps keeps force closing everytime i have GPS signal. Maps works fine. What could it be?
Thanks in advance!
Click to expand...
Click to collapse
Other nav app works
Maybe gapps fix could help here, dunno...

Straaange things happened this morning

Seeing as though there's no more BajaROM thread, I'll post this is in the general Q&A section. Of course, while I am running BajaROM, I can't be sure that the ROM had anything to do with it.
Something weird definitely happened to my phone last night... at exactly 2:28am, it would seem.
When I woke up this morning, my live background changed to a different static background, my normal keyboard (thumb keyboard) was replaced by the samsung one, my clock widget was frozen at 2:28, the battery level read 87% (after charging all night), and hasn't changed all morning, even after an hour commute of phone calls and media play... tasker had inexplicably turned off... and I'm still finding odd things.
I restarted my phone, and my clock is more current now, but my clock widget and the statusbar clock are a minute apart for a portion of every minute (like they're offset by <60sec) Tasker still didn't turn on like it should have, until I started the app to spark it... as if it was the first time I installed it. (It does the same thing when I restore the app through Titanium Backup on a new ROM install)
I checked to make sure I still have root by starting Titanium Backup... I have root, but titanium backup says it's the free version now... when I normally have the Donate (Pro) version. I had to reinstall it from the Google Play store
I have a few nightly backup/refresh items scheduled in Titanium Backup at 2am and 2:30am... so I wonder if something went wrong.
If anyone has experienced similar issues, leave a comment.
Thanks!
DrPhant0m said:
Seeing as though there's no more BajaROM thread, I'll post this is in the general Q&A section. Of course, while I am running BajaROM, I can't be sure that the ROM had anything to do with it.
Something weird definitely happened to my phone last night... at exactly 2:28am, it would seem.
When I woke up this morning, my live background changed to a different static background, my normal keyboard (thumb keyboard) was replaced by the samsung one, my clock widget was frozen at 2:28, the battery level read 87% (after charging all night), and hasn't changed all morning, even after an hour commute of phone calls and media play... tasker had inexplicably turned off... and I'm still finding odd things.
I restarted my phone, and my clock is more current now, but my clock widget and the statusbar clock are a minute apart for a portion of every minute (like they're offset by <60sec) Tasker still didn't turn on like it should have, until I started the app to spark it... as if it was the first time I installed it. (It does the same thing when I restore the app through Titanium Backup on a new ROM install)
I checked to make sure I still have root by starting Titanium Backup... I have root, but titanium backup says it's the free version now... when I normally have the Donate (Pro) version. I had to reinstall it from the Google Play store
I have a few nightly backup/refresh items scheduled in Titanium Backup at 2am and 2:30am... so I wonder if something went wrong.
If anyone has experienced similar issues, leave a comment.
Thanks!
Click to expand...
Click to collapse
This won't help you understand what's going on but for what it's worth I'm running Baja 16.1 and it's just fine. I don't use any exposed or wanam modules. Think that might be the culprit? That is if you run any..
TheAfroSamurai said:
This won't help you understand what's going on but for what it's worth I'm running Baja 16.1 and it's just fine. I don't use any exposed or wanam modules. Think that might be the culprit? That is if you run any..
Click to expand...
Click to collapse
I do run some (several) xposed mods and wanam/gravity box mods, and have been for quite some time on several devices. A string of bizarre events like that hasn't happened though.
It is strange, though, that I did install XToast just last night. This is an xposed mod that gives you more control over the toast messages received under different circumstances. Could be the culprit... not sure. I think I'll disable it and go back to BurntToast, a mod that does similar stuff.
Maybe switching from one to the other borked something?
Thanks for the input.
I also experienced some weird behaviour. I do suspect Titanium tp cause the problems, but I'm not yet 100% sure...
Not all of my issues are completely the same as yours, but still similar.
First of all, my device is a Galaxy S3 mini, CM11 installed, rooted, XPosed installed with several modules (but no Gravity or Wanam). All partitions are in ext4, external SDcard is in exFAT.
(1) root: During startup, Titanium asks an awful lot of times for boot access. Sometimes it does for 50-100 times. In the end, devices will still be rooted but startup takes a long time.
(2) startup: As mentioned: takes really long. With EVERY reboot, I get the "Android is upgrading..." message for about a minute.
This issue is solved by clearing all .odex-files with Lucky Patcher.
(3) Keyboard. I used Google Keyboard as my standard keyboard, but a while after installing/flashing (10 minutes to an hour) Google Keyboard uninstalls spontaneously (without interaction). This happened with all Keyboard versions I tried, in system and in data. And with or without it checked as primary keyboard in language & input settings. (because of those issues I switch to SwiftKey)
(4) Background: Background (custom wallpaper) disappears after a crash, and instead I get a static generic Android wallpaper. Also, every time I try to set my wallpaper back, device instantly reboots. (soft reboot which crashes and goes into a full reboot)
(5) Clock freeze: I've had those clock freezes a few times, but months ago. I think in my case it was due to some bad code in the ROM, not Titanium.
(6) Root: Even though in SuperSU settings I asked to remember autorisation, and automatically grant access, but after every boot, I had to grant permission to all apps using root access over and over again.
In order to try to solve my problems, I changed a few things.
- Google Now Launcher + XGelSettings instead of Nova Launcher. This didn't solve any of these problems, but I do like GNL more now
- I'm using Titanium Backup 6.1.5.4 stead of latest version, installed as a data app.
- I'm using SuperSU 1.98 instead of latest version, flashed as a system app.
- I'm using an older ROM version (CM M5 instead of CM M9/latest)
Most of my issues are gone now. I didn't check for (3) anymore.
armadiljo said:
I also experienced some weird behaviour. I do suspect Titanium tp cause the problems, but I'm not yet 100% sure...
Not all of my issues are completely the same as yours, but still similar.
First of all, my device is a Galaxy S3 mini, CM11 installed, rooted, XPosed installed with several modules (but no Gravity or Wanam). All partitions are in ext4, external SDcard is in exFAT.
(1) root: During startup, Titanium asks an awful lot of times for boot access. Sometimes it does for 50-100 times. In the end, devices will still be rooted but startup takes a long time.
(2) startup: As mentioned: takes really long. With EVERY reboot, I get the "Android is upgrading..." message for about a minute.
This issue is solved by clearing all .odex-files with Lucky Patcher.
(3) Keyboard. I used Google Keyboard as my standard keyboard, but a while after installing/flashing (10 minutes to an hour) Google Keyboard uninstalls spontaneously (without interaction). This happened with all Keyboard versions I tried, in system and in data. And with or without it checked as primary keyboard in language & input settings. (because of those issues I switch to SwiftKey)
(4) Background: Background (custom wallpaper) disappears after a crash, and instead I get a static generic Android wallpaper. Also, every time I try to set my wallpaper back, device instantly reboots. (soft reboot which crashes and goes into a full reboot)
(5) Clock freeze: I've had those clock freezes a few times, but months ago. I think in my case it was due to some bad code in the ROM, not Titanium.
(6) Root: Even though in SuperSU settings I asked to remember autorisation, and automatically grant access, but after every boot, I had to grant permission to all apps using root access over and over again.
In order to try to solve my problems, I changed a few things.
- Google Now Launcher + XGelSettings instead of Nova Launcher. This didn't solve any of these problems, but I do like GNL more now
- I'm using Titanium Backup 6.1.5.4 stead of latest version, installed as a data app.
- I'm using SuperSU 1.98 instead of latest version, flashed as a system app.
- I'm using an older ROM version (CM M5 instead of CM M9/latest)
Most of my issues are gone now. I didn't check for (3) anymore.
Click to expand...
Click to collapse
Thank you for the information. I kind of suspect that Titanium Backup had something to do with my problems, as well, since it happened right around the time that a scheduled action was to take place. I think that TB was still in the middle of the previous operation at 2am when it tried to start the next one at 2:30. This has never caused a problem before, but maybe it was at the wrong place at the wrong time, as odd as that may sound.
Your problems seem to be a more constant hassle. Especially the parts about granting SU access several times. I'm leaning toward the fact that your external SD card might interfere a little. External memory is handled a lot differently in kitkat builds, which CM11 is. In newer custom ROMs, there are attempts made to "fix" it... but in your case, maybe it was counter-intuitive.
The issue is that, to paraphrase... Kit-Kat imposes a lot of data access restrictions on external media. So... if you create a file in one app... you can't modify that file in another. That's a bastardization of the whole thing, I'm sure... so look up the particulars from someone more qualified than I. haha
If I were you (and I had a few hours to burn)... I'd back up everything on your external card and your internal memory (a good idea in any case),
clear EVERYTHING and reinstall the latest versions of everything without the external card in your phone. See if you still have issues. If you don't, then the card might be a problem. Then, wipe the card and put it back in your phone, and let your phone reformat it. At that point, copy your backed-up card data to your external card in whatever way is best to keep KitKat from messing it all up again.
Luckily, I don't have issues with my external card, except for the fact that, say, if I want to put a picture of my son as my wallpaper or notification shade background... if I pick a file from the card, it won't load after I restart my phone. For stuff like this... make sure that you put the pic ON YOUR PHONE STORAGE. Consider it like this... you wouldn't have a lot of luck if your PC's desktop background or screensaver ran from the CD drive, as opposed to your hard drive.
@DrPhant0m
I already went to that process of backing up, wiping and so on. Actually, I already did it twice.
The first time, I cleaned my device, installed latest versions of everything, went through the restoring process. But most of my mentioned issues still existed.
The second time, I cleaned my device again, did about exactly what you mentioned, but I restored some older versions of the ROM, SuperSU and Titanium Backup Pro. And right now, my issues are gone!
Actually, I didn't realise there are so many KitKat-related issues with SD. Maybe my pictures indeed are/where stored on a faulty SD. But it's reformatted now, and it works. And I actually don't know if that picture is stored internally or externally, I selected the picture with/by Google Photo. No idea how it handles is
I'm not saying Titanium certainly will be the bad guy, but I'm quite sure it plays it's part in it. Other issues are caused by the custom ROM. In the last few months, developers of that ROM don't give a **** about solving issues, and introduce one new feature after the other, most of them still highly experimental. Maybe that's another problem I can't control at all
I have found that Titanium always deletes my custom wallpaper and replaces it with the Samsung default every time I do a backup. It also changes my keyboard (normally Hacker's Keyboard) back to Samsung keyboard. It started doing this several updates ago.
Verizon Note 3, 4.4.2, NC4, stock rooted
Titanium Free 6.1.5.6
Michele31415 said:
I have found that Titanium always deletes my custom wallpaper and replaces it with the Samsung default every time I do a backup. It also changes my keyboard (normally Hacker's Keyboard) back to Samsung keyboard. It started doing this several updates ago.
Verizon Note 3, 4.4.2, NC4, stock rooted
Titanium Free 6.1.5.6
Click to expand...
Click to collapse
Every time you do a backup it does this? That's bizarre. Or, do you mean when you restore a backup? I want to say to update to the paid version and see if it fixes it, and if not... request a refund.
What info do you back up when this happens? I could see restoring a backup working against you. For instance, if you restore your keyboard and maybe even some language/input system files... it might default back to the standard keyboard because your confirmation to use a 3rd party keyboard (which could theoretically log all of your keystrokes) is no longer valid.
The background thing is a different story. When Titanium Backup works well... when I restore all of my "MUST HAVE" stuff after a new ROM install... it will restore my live wallpaper, too. There are often times that TB will NOT "work well" and the widgets and wallpaper (among other things) aren't restored properly... not to mention the fact that I can not get my bluetooth pairings and known wifi networks to restore, whether I use snapshot or XML.
DrPhant0m said:
Every time you do a backup it does this? That's bizarre.
Click to expand...
Click to collapse
Yes. It is.
DrPhant0m said:
Or, do you mean when you restore a backup? I want to say to update to the paid version and see if it fixes it, and if not... request a refund..
Click to expand...
Click to collapse
No, I don't mean upon restoration. I mean I take a full backup (user apps + system apps), go off for a cup of coffee, come back, see that it completed OK, exit TI, and then I see that my background is back to the Samsung default and it I open something that needs keyboard, the keyboard is also back to Samsung default. I guess it was never enough of a bother for me to go to the trouble of buying it and then complaining. I figure that for free, I can put up with a minor annoyance.
DrPhant0m said:
What info do you back up when this happens? I could see restoring a backup working against you. For instance, if you restore your keyboard and maybe even some language/input system files... it might default back to the standard keyboard because your confirmation to use a 3rd party keyboard (which could theoretically log all of your keystrokes) is no longer valid.
Click to expand...
Click to collapse
I can see where you're thinking, but it happens right after *doing* the backup. I haven't even had the need to do a full restore yet, so I don't know what that would do.
DrPhant0m said:
The background thing is a different story. When Titanium Backup works well... when I restore all of my "MUST HAVE" stuff after a new ROM install... it will restore my live wallpaper, too. There are often times that TB will NOT "work well" and the widgets and wallpaper (among other things) aren't restored properly... not to mention the fact that I can not get my bluetooth pairings and known wifi networks to restore, whether I use snapshot or XML.
Click to expand...
Click to collapse
It's very odd, that's for sure.

Android O Public Beta opinions

Today I installed the Public beta version of Android O, it has a really nice redesign and some cool new functions, but, how is the performance?, I would like to share with you my experience, and hope you guys can share your experience here too.
Im going to be direct:
*Notification sounds are delayed
*Ambient display just work tapping two times
*Recent app lags
*Clean data option (on storage) is gone.
*Slowdown in some apps (guess just have to wait for an update)
I did a "wipe cache partition" after install the update, I didnt clear the data from storage cuz the option is gone.
New info: 05/24 (or 24/05 from spanish people)
For those that are having a really bad experience with Android O this could help:
I dont have a USB-C to Standar USB wire and I really wanted to make my phone works better, flash a stock rom is not an option for me today, so I did this (do a proper back up and do it under your own risk)
*Back up everything.
*Unroll from Beta
*Downgrade to Android N (that implies lost everything)
*Config the device as a new one BUT dont log in your google account, just connect wi-fi (that implies LOSE APP CONFIGURATIONS and Wi-Fi passwords)
*Regist your device to Android O again
*Wait for the update and install it.
*Configure the whole phone, apps and everything (remember, if you config it as a new device before going back to Android N the device will not download your previos configuration as settings config, apps config, wi-fi saved passwords etc etc.
I did it and Im still configuring everything but the phone works better that the first time I installed Android O through OTA without wipe the phone.
I will keep testing the phone in this way and I will let you guys know if it really helps in long terms (I mean, if next week the phone still works fine means that all the effort worth it)
PD: Just one thing, if Ambient display doesnt work for you, just, turn the option off, then On, and then power off the phone (power off, not a restart), turn it on and thats all.
NOTES: Going back to Android N could cause some stuff stop working like, rotation, gps, etc.
If you do a factory reset in Android O that could cause a bootloop, be careful and just try it IF you can flash the phone (remember the USB-C to Standar USB wire, my phone didt came with one...)
IMPORTANT:
If you went back to Nougat and found that stuff like GPS, rotation etc was not working, here you have a solution that allow you back to Nougat without those problems.
In Android O:
*Unroll from Beta program.
*Install the downgrade package
*Start your phone loging in your account but disable everything and dont restore your configuration. (Just use your account for go to the main screen)
*When finally you get the control of the phone DO A FACTORY RESET (from settings)
*This time configure averything as you want (restoring apps and configurations) and thaths all!, try to test everything and this time all will be working as always!
No root, no flash, just doing that
I installed by flashing the factory image. Device feels a lot sluggish when opening app drawer, recents, App info. I read various comments on Google+ that their device feels snappier and fast than Nougat but it took them a while before device gets settled in. So, I will give it a few good hours before judging on performance.
same feeling but still usable
Runs amazing on my device
takes ages to take a shot with hdr on
Things I've found not working:
1. Lock screen app resets after phone is turned off or restarted, and has to be selected manually again
2. Force activities to be resizeable in developer options not working
3. UI lags more often
4. Picture in picture more not working ( at least for me)
*I'll add more when I find
Is Gmail working? That was the thing that was constantly messed up for me. Everything else was fine
mikeprius said:
Is Gmail working? That was the thing that was constantly messed up for me. Everything else was fine
Click to expand...
Click to collapse
Yes it is working fine.
The reason for the UI slowdown I think it is because recents preview images are bigger (more resolution).
It's quite good for a beta.
- Some UI lags
- Sometimes apps load a little slower than 7.1.2
- Picture in picture doesn't work for now (Only for youtube red users right now)
I've noticed the battery charges faster when the phone is being used compared to 7.1.2
---------- Post added at 10:07 AM ---------- Previous post was at 10:02 AM ----------
Billys20 said:
It's quite good for a beta.
- Some UI lags
- Sometimes apps load a little slower than 7.1.2
- Picture in picture doesn't work for now (Only for youtube red users right now)
Click to expand...
Click to collapse
For picture in picture mode
Use the hidden navigation bar tuner in SystemUI Tuner. Add a navigation button and select the button type to be “keycode” and look for keycode #171. Once you’ve done that, your navigation bar will now have a button that, when pressed inside of a supported app, will toggle PiP.
bootloop !
hi my device stuck in bootloop after update on google Logo
but recovery mode is working , i wiped cache and data and now stuck in android boot animation and restart
my device is dead?
Some differences I've noticed in comparison to the 1st dev preview:
* Notification tray redesigned again, I do not like the lightgrey tone, but the layout of the elements does feel abit more mature compared to dp1.
* It seems more stable, less lags - altough animations seem to lower in framerates at some moments, triggering the Recently Used function delivers low framerates always (Project Butter failing?)
* In the 1st dp, the Sense 7 keyboard I use would crash, works again in dp2
* Images are misaligned in the Telegram app, I do not notice this in other apps, but everything was alright in the dp1 regarding this.
* Not sure but I feel like the Settings app has some additional icons, still not complete though. Some titles in the Settings.apk now also inherit the accent color.
* The LTE icon is now displayed in full, the wlan icon is shown with disabled status in the statusbar if its disabled. The muted sign has returned.
* Notification icons in the statusbar seem to have a wrong top-padding, so they misalign ~1-2px
The PiP mode should come available once the YouTube app gets updated with the feature, it's just that the api was made available with this release.
abolfazl.h said:
hi my device stuck in bootloop after update on google Logo
but recovery mode is working , i wiped cache and data and now stuck in android boot animation and restart
my device is dead?
Click to expand...
Click to collapse
Try reflashing the factory image with fastboot. If the device was dead, it would bootloop in the recovery aswell.
guys how to download the latest beta ?i mean developer preview 2 ..on DP site i have found opp2 but dated to 20\4 isnt it old ?
tornido067 said:
guys how to download the latest beta ?i mean developer preview 2 ..on DP site i have found opp2 but dated to 20\4 isnt it old ?
Click to expand...
Click to collapse
20/04 is the beta image, give it a try. So far it's pretty good and has stabilised on my phone after an initial few hours of sluggish behaviour.
Settings app keen crashing, anyone got a solution?
ishrak619 said:
Settings app keen crashing, anyone got a solution?
Click to expand...
Click to collapse
factory reset
---------- Post added at 01:52 PM ---------- Previous post was at 01:51 PM ----------
Is the Pixel Launcher included or is GNL still used?
Gnl
Sent from my Nexus 5X using Tapatalk
After few hours of using it everything seems smooth now. But Recents are lagging every now and then.
To me everything is lagging as hell
Sent from my Nexus 5X using Tapatalk

Categories

Resources