• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

PSA Sneak Peek for Android "L" is out!!!!

Rxpert83 said:
App incompatibilities are to be expected. I haven't run into any yet, but haven't installed too many non google apps
Click to expand...

The two incompatibilities I've seen are Firefox and HBO Go. I also had an issue with Lightflow; initially it worked fine but, after rebooting, it kept forcing the phone to restart.
 
Well. The good thing about the prelease peek is when it actually rolls out to us in the fall we won't have most of these issues.
 
If I didn't have to work in 8 hours, I would be totally balls deep into fastboot right now. Can't wait to see the new version but I think I'll start with the nexus 7 first, phone after.

Enjoy everyone! The videos look great!
 
rhray said:
If I didn't have to work in 8 hours, I would be totally balls deep into fastboot right now. Can't wait to see the new version but I think I'll start with the nexus 7 first, phone after.

Enjoy everyone! The videos look great!
Click to expand...

Lol, I hear you there... I just pulled out! ;) That was probably the longest ROM flash session ever! At one point you just can help but think, Man is this thing gonna boot!
Finally It booted up and Yeah it's actually pretty awesome!
Everything seems to be working perfectly. I'm impressed with it so far. Its only a trial run and they will make huge improvements with it in the next coming months.
So far, I really like the UI, keyboard, notifications and status bar.
Still have TWRP and root with some apps too.
 
Have it running fine via MultiROM. Won't have time to play much until much later, but it's smooth and fast. Need my production phone, so MultiROM is a great option.
 
Does anyone know how Google will provide updates to the Developer Preview? I would suspect they will do OTA updates to users that are running the preview but don't want to assume.
 
vandyman said:
Yeah! I guess that Titanium is a no go for now.
Bummer...:(
Click to expand...

As I recall, TB also had problems when Kit Kat was first released. I would expect fixes to come quickly. I'm sure all the major devs are playing with this.
 
Hook said:
As I recall, TB also had problems when Kit Kat was first released. I would expect fixes to come quickly. I'm sure all the major devs are playing with this.
Click to expand...

A completely non-educated guess, but I had issues using an older version of fastboot to update my phone. Once I got the newer version of fastboot it worked great. If TiBu and He are based on adb, then it's entirely possible they will not work until updated to the latest adb.
 
So quick update, using the latest adb I can restore files backed up by Helium. I don't know how to do a batch restore, so far I've only figured out how to do one file at a time.

./adb restore /path/to/backup.ab

Additionally, check this out:

Using whatever old adb is installed on my mac:
~/Downloads/android-sdk-macosx/platform-tools $ which adb
/usr/local/bin/adb
~/Downloads/android-sdk-macosx/platform-tools $ adb version
Android Debug Bridge version 1.0.29
~/Downloads/android-sdk-macosx/platform-tools $ adb devices
List of devices attached

Using the newest version of adb downloaded yesterday:
~/Downloads/android-sdk-macosx/platform-tools $ which ./adb
./adb
~/Downloads/android-sdk-macosx/platform-tools $ ./adb version
Android Debug Bridge version 1.0.31
~/Downloads/android-sdk-macosx/platform-tools $ ./adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
*************** device

(I blanked out the serial number since I can't remember if that's sensitive or not)

I think it's clear that an older version of adb doesn't recognize the phone, for whatever reason, so this is likely the problem.
 
morgankslade said:
That is a good idea.

Im in the process of making a .zip from TB of certain user apps with data.
Flashed it and it works.

Thank you

A few apks don't work like file explorers. But games and other Private business apks work.
Click to expand...


Yep TWRP 2.7.1.1 is working fine here as well. Backed up and restored Android L and DU without any problems.
I flashed the Android L modified boot.img then flashed the SuperSU.zip, which gives root access. Root browser is working fine, SuperSU granted permissions.
Haven't had a chance to see what other root apps are working or not.
 
I'm trying to flash a custom recovery but have run into a problem. Since I flashed Android L my PC has been unable to detect the device in fastboot mode. (It worked fine before.) With USB debugging enabled in Android, I send the command "adb devices" and my PC can see it immediately, suggesting that it's not a driver issue. I reinstalled the drivers anyway and there is no change. In Android I can see it, in fastboot I can't. Before flashing Android L I had no problems seeing it either place.

So I changed strategies and tried flashing recovery via zip file in the stock recovery, but it won't load. I just get the Android with the red triangle coming out of his chest.

Do you have any idea why it's doing this after flashing Android L? Can I safely flash the recovery in Android instead of fastboot?

TIA
 
Can you save TWRP 2.7.1.1 to phone. You will find the link somewhere (Google It)
Download and install Flashify from store.
Flash TWRP zip through Flashify.

Hope it helps.
 
morgankslade said:
Can you save TWRP 2.7.1.1 to phone. You will find the link somewhere (Google It)
Download and install Flashify from store.
Flash TWRP zip through Flashify.

Hope it helps.
Click to expand...
This is a chicken & the egg scenario for me. Flashify, TWRP's installer and ClockworkMod ROM Manager all require root access to flash a recovery. I can't root because my stock recovery isn't loading. That's why I asked if I can flash a recovery.img to the recovery partition from Android. My PC can see the device from Android, but not fastboot.
 
To my knowledge, you can't use the fastboot tools using a chromebook. I haven't tried using the crouton hacked ubuntu to try it though. That might be your best option if you have to use a chromebook.
 
this is semi applicable to this thread and I also figure the most technically savvy eyes will also be here too.

Question: Is there a difference between a factory reset (with automatic restore turned on) and flashing a stock image of the same flavor (with automatic restore turned on)? By difference I mean will there be any app or data differences?
 
You must log in or register to reply here.
Back
Top Bottom