yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] los93sol:
Glad to see more developers taking an interest in this now. I have made some significant progress over the weekend. I did a checkout of the l preview branch, merged shiny's tree in and made the required changes to get it to compile. The build doesn't produce a fully working ramdisk and kernel, but it was valid enough that I was able to hand edit it to get the l preview branch booting up on my Toro, this is build 4.4.4.43.43.43. Now, this in and of itself doesn't mean a whole lot, but it gave me a fresh libc.so and most of the other libs that are dependencies for L. I should note that tf_daemon and libsec-ril_lte.so will need to be hacked to eliminate MD5_Init from the linked tables in both binaries and I had to disable both of those proprietary binaries in init to get the rom to boot. That means, as you would expect, it is VERY unstable, but it boots! So, having that working I then merged in app, app-priv, and framework from hammerhead's L preview image, the result...better than before, but still not quite there! It gets all the way up to art trying to do it's thing then dies there, but that's a whole lot further than we were before, zygote is actually starting up at this point and we're onto the framework!!! I am going to mess around with the proprietary libs first as I believe that the same method to fix those can be used to fix the new art libs as well.
[Samsung Galaxy Nexus] sykopompos:
Send me over the logcat, I think I might know why

Sent from my LG-D851
[Samsung Galaxy Nexus] armada786:
I don't know how much I can contribute but I'll take a look at it as well. Perhaps more hands will help. EDIT: I should mention I'm testing on Toro too, if that helps.
[Samsung Galaxy Nexus] los93sol:
Here is the latest for anyone who is interested https://drive.google.com/file/d/0B_q0CDQXX32nbFNhNzQwck5SWDA/edit?usp=sharing
[Samsung Galaxy Nexus] los93sol:
Here is a custom built libc.so that allows to enable RILD and tf_daemon in init.rc and init.tuna.rc for anyone trying to get this to work.

https://drive.google.com/file/d/0B_q0CDQXX32nZTFNT01od1lvWkU/edit?usp=sharing

I'm pretty stubborn but I think we might have to wait for sources to drop. With this new libc.so all the symbols are included to meet all the dependencies of libandroid_runtime.so from hammerhead, but once you meet them all it blows up with an "Illegal Operation" error or something to that effect.
[Samsung Galaxy Nexus] armada786:
Is framework.jar from KitKat or L in this case? Something seems to be screwing up in there and cause ART to bite the dust. I don't know what you've considered in this case, just throwing ideas at the wall at this point.
[Samsung Galaxy Nexus] sykopompos:
I remember that error. It is kicking those out because of the SDK framework. Try switching over to the n7's framework like we did (use the n5 framework-res. Apk though)

Sent from my LG-D851
[Samsung Galaxy Nexus] whoshotjr2006:
hey sykopompos, i downloaded los93sol's updated rom zip and swapped the framework folder except framework res apk which i even made sure that was an n5 copy, and im getting bootloops from libcore and ICU stuff.

relevant logcat

looking here i found where you and some others start talking about it

would you happen to remember what you guys did to get past that? im quite stuck.

thanks again for everything
[Samsung Galaxy Nexus] sykopompos:
I believe that is when we switched over to the full n7 base instead of fighting it with aosp. Now I have been trying to work it backwards to try to get back to an aosp base

Sent from my LG-D851
[Samsung Galaxy Nexus] los93sol:
It's fighting libcore and ICU because libandroid_runtime.so is from KK. When I try to use libandroid_runtime.so from razor or hammerhead I can meet all the dependencies, but then we get "Illegal Instruction" when running the binary manually. I believe this is happening because of something cross-compiled, but I have no clue how to get more information about what is causing it There are a few calls back into the framework from libandroid_runtime.so like getISO3Country, getISO3Language, and getaddrinfo that I have patched up since posting that last zip. I will post up the patched frameworks later.

Note that I may change things up slightly, I am building from the l-preview branch. I merged in all the toro build files and have modified the tree slightly to include some missing things that our proprietary binaries require, but I believe we need to study the code here https://android.googlesource.com/platform/art/+/l-preview/runtime/ and probably need to slightly change things here. It appears google has not given us all the tools we need.

I actually have one other idea before I go that route though.
[Samsung Galaxy Nexus] armada786:
I was digging into that last error the other night. What's the source for your framework for this? Hammerhead or razor? Try using the framework from n7 but the framework-res from n7 like sykopompos suggested.
[Samsung Galaxy Nexus] los93sol:
I've tried both already....I actually traced that problem down, it has to do with art runtime, it's appending some invalid arguments to the dex2oat options. I was able to manually force it to get further in the boot process, doing some tests now, but I see art has been very active in AOSP's master branch so I'm also doing a checkout to build against master.
[Samsung Galaxy Nexus] armada786:
I'm looking at the offending function and it seems to throw the error because of a null pointer.

if (image_classes.get() == nullptr) {
LOG(ERROR) << "Failed to create list of image classes from '" << image_classes_filename <<
"': " << error_msg;
return EXIT_FAILURE;
}

It's another scavenger hunt to figure out where this dies. I'm looking at it and I'll fill you in if I find anything.
[Samsung Galaxy Nexus] los93sol:
Cool, I looked at the master branch and it does not append the extra arguments when dex2oat is called, pretty sure that was the root cause, it was searching for preloaded classes when it should not have been, omitting the image classes argument resolved it when running manually. I can easily edit art in the current build against l preview or build against master to resolve it. I might try both just for fun, but ultimately it's looking like we should be building against master.
[Samsung Galaxy Nexus] armada786:
Great. I'm sure this'll bring on another round of errors to handle, but if ART is fixed that's still a big step in the right direction.
[Samsung Galaxy Nexus] sykopompos:
I'm just waiting for the insanity to take over for him.

He has been at this for weeks now and still hasn't gotten it yet and he has put a **** ton of work into it trying to get it

Sent from my LG-D851
[Samsung Galaxy Nexus] Carlos_Manuel:
This may be interesting:

http://www.androidpolice.com/2014/0...ges-for-nexus-7-razor-and-nexus-5-hammerhead/
[Samsung Galaxy Nexus] sykopompos:
I got a chance to look over this. It does indeed have some newer closed source stuff but the base is still the l-preview branch and not newer aosp so don't expect any bug fixes with it really.

I can tell by the ramdisk. I spent enough time down here with these selinux files and I know the changes that have been made in aosp since and something from 3 weeks ago is not in here.

Some new system apps and some new libs but I wouldn't expect anything huge in bug fixes because it really is not an update﻿

Sent from my LG-D851
[Samsung Galaxy Nexus] los93sol:
EDIT 1: Whoops! That's actually not the latest! Give me a few to get the zip updated and I'll ammend this post with the corrected information

I haven't quit on this yet, but I have hit another roadblock that I have sunk quite a bit of time into figuring out. If anyone is interested please take a look at this logcat http://pastebin.com/AdFLvP4z

I'm uploading the latest flashable zip now as well, here are the details of this build...

Built against AOSP's master branch

Disabled the PIE security check so our pvrsrvinit can load up properly

Added MD5_Init symbols in libc which are required for our RIL

Full app folder from hammerhead's L preview image

Full app-priv folder from hammerhead's L preview image

Full framework folder from hammerhead's L preview image, except core-libart.jar, that file is from AOSP's master branch

Fully permissive sepolicy, special thanks to [MENTION=1050103]sykopompos[/MENTION] for the tip on how to accomplish this

Patched setOomAdj function back into framework.jar

Note that I tested this build with the framework from AOSP's master branch and it does indeed boot up to the launcher.

I'm pretty much drained on this port and looking for someone serious with a device to get in here with me and try to figure this out and get it booting the rest of the way! We are so close, but for me I've sunk way too much time into this and that last 100 feet looks like miles at this point.

Grab the flashable zip here https://drive.google.com/file/d/0B_q0CDQXX32nYUJ4bUtxOHRFWjA/edit?usp=sharing

Remember, this still does not boot, the most excitement here right now is that you can see the boot animation.

I also recommend flashing ChainFire's updated supersu for L which you can get from https://drive.google.com/file/d/0B_q0CDQXX32ncTNHcGMtbDN1V3c/edit?usp=sharing

ChainFire's zip just makes getting logs off the device a bit easier since you can pull dmesg straight from the device while it's running.

Well, that's all I've got for now, again, I'm looking for someone to get their hands dirty and dig into this with me so if you're interested just reach out to me and let's tackle the last little bit of it.
[Samsung Galaxy Nexus] sykopompos:
I wish I had one so I can work through it with you.

Oh BTW, there is a line, I think it is in the init.toro.rc that says restrict dmesg, delete that line and then you don't need su anymore to get the dmesg

Sent from my LG-D851
[Samsung Galaxy Nexus] armada786:
Thanks for all the hard work. Maybe with some more work it'll be usable, but there isn't too much longer to wait for the full L source to hit AOSP, which will be much easier than this. I think we can be patient. In the meantime, I may keep trying things with this. EDIT: If you help me set things up I can help build. I'm terrible with Android's build tools because I've used them all of 3 times, but I know enough to actually help with this. I'm reading through the logcat right now to see where to start.

I can always be guinea pig for build if you want someone that actually knows something or other. I've only built Android a couple times before for Iconia A500 (picasso), but if I can wrap my head around it with regards to porting I can try compiling my own too.
[Samsung Galaxy Nexus] sykopompos:
It is already built, he is replacing files with aosp ones till it errors then going into smali'ed framework files, making edits and testing again

Sent from my LG-D851
[Samsung Galaxy Nexus] armada786:
Well, dex2oat dies on trying to compile TrustManagerImpl.java, but I don't know why. I'm digging through dex2oat.cc and oat_writer.cc to see what there is. I'm trying to find where a method called CHECK is defined to maybe figure out how to fix TrustManagerImpl.
[Samsung Galaxy Nexus] sykopompos:
It could be something in the new frameworks, the problem with going from the port to aosp is some things are already fixed in aosp or moved past vs what is in the preview

Sent from my LG-D851
[Samsung Galaxy Nexus] armada786:
Pretty sure the problem child is this method in oat_writer.cc

class OatWriter::InitImageMethodVisitor : public OatDexMethodVisitor {
public:
InitImageMethodVisitor(OatWriter* writer, size_t offset)
: OatDexMethodVisitor(writer, offset) {
}
bool VisitMethod(size_t class_def_method_index, const ClassDataItemIterator& it)
SHARED_LOCKS_REQUIRED(Locks::mutator_lock_) {
OatClass* oat_class = writer_->oat_classes_[oat_class_index_];
CompiledMethod* compiled_method = oat_class->GetCompiledMethod(class_def_method_index);
OatMethodOffsets offsets(0u, 0u);
if (compiled_method != nullptr) {
DCHECK_LT(method_offsets_index_, oat_class->method_offsets_.size());
offsets = oat_class->method_offsets_[method_offsets_index_];
++method_offsets_index_;
}
ClassLinker* linker = Runtime::Current()->GetClassLinker();
InvokeType invoke_type = it.GetMethodInvokeType(dex_file_->GetClassDef(class_def_index_));
// Unchecked as we hold mutator_lock_ on entry.
ScopedObjectAccessUnchecked soa(Thread::Current());
StackHandleScope<2> hs(soa.Self());
Handle<mirror::DexCache> dex_cache(hs.NewHandle(linker->FindDexCache(*dex_file_)));
mirror::ArtMethod* method = linker->ResolveMethod(*dex_file_, it.GetMemberIndex(), dex_cache,
NullHandle<mirror::ClassLoader>(),
NullHandle<mirror::ArtMethod>(),
invoke_type);
CHECK(method != NULL) << PrettyMethod(it.GetMemberIndex(), *dex_file_, true);
// Portable code offsets are set by ElfWriterMclinker::FixupCompiledCodeOffset after linking.
method->SetQuickOatCodeOffset(offsets.code_offset_);
method->SetOatNativeGcMapOffset(offsets.gc_map_offset_);
return true;
}
};

It looks like method is, in fact, null here because of some problem in the linking step. I can't say exactly why, though, because other framework packages are getting by just fine. By the way, I was wrong earlier and it's looks like it's actually acting on the conscript.jar package in framework and something in TrustManagerImpl (within the conscript pakage) is goofing things up. Maybe try using an AOSP-built version of this too?
[Samsung Galaxy Nexus] sykopompos:
I believe he is. There is new encryption stuff in the vold so that might be what it is

Sent from my LG-D851
[Samsung Galaxy Nexus] armada786:
Perhaps. It's bothering me that this is dying in oat_writer because the method that is supposedly null, the constructor for TemplateManagerImpl, is actually there. Unless I'm misunderstanding what oat_writer is supposed to be checking for there entirely.
[Samsung Galaxy Nexus] sykopompos:
I'm not sure and it might be that isn't even it. There has been a lot of changes to aosp especially with art so that might have something to do with the new patch_oat feature which checks if something has already been dex'ed

Sent from my LG-D851
[Samsung Galaxy Nexus] armada786:
Is it possible to build the l-preview branch of ART at all? Since the sake of the port is just to be usable, even reaching the Welcome screen/launcher would an achievement and if using that version of ART works it furthers that end. You seem to be more in the know about this, what with moving the N4 port to AOSP.
[Samsung Galaxy Nexus] sykopompos:
Los tried that already with L preview branch and didn't get all that far. We have been going through trying to get it for the past couple weeks on hangouts.

The problems are that the egl drivers get broke working from the preview back to aosp because of open gl 3.1 not being in the source plus the renderscript. Then you also got new encryption in vold, new music player files so that breaks merging in correct sound drivers, new Bluetooth stuff so Bluetooth on half works.

My suggestion and I think is the best route is to take the smali and try working that into aosp as more of a back porting thing grabbing the new hooks. Then we can upgrade the whole base with all new files.

I guess the easiest way might be to build the L preview branch for the n7 and then break that into smali and do diff's trying to find the differences and then pull them in

Sent from my LG-D851
[Xperia Z2 Tablet Accessories] Felborn:
So, I'm about to leave for a holiday for a couple of weeks, and a MHL adapter for my Z2 tablet would be nice. I see Sony has a cable, but that's like 38$ in the local story, and I can find MHL 3.0 adapter for 4-5$ on Ebay. Would any MHL 3.0 adapter work, or does it have to be the Sony cable? I see many of the brands on Ebay mention Samsung, any reason why this would not work?
[Xperia Z2 Tablet Accessories] Pondy:
If you find one that works, can you let us know either way? I am also interested in this!
[Xperia Z2 Tablet Accessories] fribriz:
I bought one from the local accessories store - works out of the box on my Z2 tab. Just ensure that it has USB power
[Xperia Z2 Tablet Accessories] Felborn:
I got a Belkin hml adapter with input for power, worked on my Philips TV atleast

Sent fra min SGP511 via Tapatalk
[Xperia Z2 Tablet Accessories] knightnz:
It'll be MHL 1.0 most probably, not 3.0 and probably not even 2.0.
[Xperia Z2 Tablet Accessories] davypaul:
the cheap ones work...

See my response on another thread

1080P-Micro-USB-MHL-to-HDMI-HDTV-CABLE-ADAPTER-For-HTC-One-M8-LG-Sony-Xperia-Z1-/171308010294? item27e2c0cb36

but this one worked for me for a GBP 'fiver'
[Samsung Galaxy W I8150] G Gabi:
Hi all,

UPDATE: issue solved, see below details.

Sorry that I'm posting my question here and not in the CWM thread, I tried but the XDA won't allow me to add a reply in the tread (see picture).

I can't get into recovery mode.

I flashed recovery-clockwork-6.0.4.5-ancora.tar.md5 using Odin 4.44, the flash passed.

When the phone is off, I press power+vol up+hone - I get a loop with Samsung logo, it shows for a second, disappears for 3-4 seconds and appears again.

Once I release the buttons, the phone will boot to the ROM (2.3.6).

I believe the CWM is installed. When I do factory reset via the phone menu (menu-->Privacy-->Factory data reset) the phones shows the recovery. See pictures.

How can I access the recovery?

I want to try the CM9 ROM.

Thanks!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

UPDATE:

Never mind, I have solved my issue (it took quite a time).

1. Turn off the device.

2. Press Power+vol up+home

3. Once Samsung logo shows on the screen - release ONLY the power button (continue pressing vol up + home).

4. U R done.
[Ubuntu Touch Ports to Android] Arwynj:
can someone make the latest ubuntu touch for n7100? I want to use it as my daily driver
[Nexus 5 General] bcollado:
Hi everyone,

there are obviously tons of Android L threads already, but I wanted to post simple instructions for getting the developer preview up and running and also back to your previous version.

Without talking much more, here are the steps...

1. Make sure you have a custom recovery installed (I suggest TWRP 2.7.0.0 or higher, I did not test with CWM so caution for those users)

2. Make a full nandroid backup (System, Data, Boot) of your current system. After the backup completes, restart your device and copy the nandroid backup file to your PC. (The file should be located in the TWRP/Backup section of your device)

3. Make sure you have Android SDK installed, https://developer.android.com/sdk/index.html (Open SDK Manager and check off Android SDK tools, platform-tools, and build-tools as well as the entire section of Android L. Click Install packages and make sure that all of those files install)

4. Download and extract the Developer Package from here http://developer.android.com/preview/setup-sdk.html#top (the download link is under step 1 in the "Install the L Preview System image" section)

5. Place the extracted Developer Package files into your platform-tools folder of your SDK folder location

7. Boot your device into fastboot mode by powering off and then powering back up by holding Volume Up + Down + Power (Let the device stay in this mode during the entire process)

8. Open command prompt and type "chdir (copy and paste the file directory of your platform-tools folder here)"

9. Type "adb start-server" this is just to ensure adb is running. Then, while still in the directory of your platform-tools folder, type "flash-all" (You may get errors with it unable to flash some ".sig" files, but that is ok. (After the files flash, your phone will automatically reboot to the boot animation, if you are on this screen for a while, just be patient. The first boot takes quite a while do to the change to ART)

Your phone should now be running on Android L. The next steps will be for returning back to your previous install, while also backing up Android L and being able to switch between the 2. Installing Android L deletes your custom recovery that you had and replaces it with a stock one. In order to make backups and return to your previous system, you must reinstall TWRP or CWM which is explained below.

10. You can install TWRP simply by using the Nexus Root Toolkit by WugFresh XDA Thread: http://xdaforums.com/showthread.php?t=1766475 Mirror: http://www.softpedia.com/get/Mobile-Phone-Tools/Others/Galaxy-Nexus-Root-Toolkit.shtml (Open the Toolkit and click Launch under Advanced Utilities. Then, under Boot/Flash Image click the Flash (Permanent) radio and click recovery. Select latest TWRP and follow the instructions.

11. After TWRP installs, make a backup of your current system (Android L)

12. Reboot your device, when powered up, place your first backup that you made (Before "L") into your TWRP/Backups folder.

13. Now in TWRP you have both your L backup and your old backup. You can restore either and then switch between the 2.

14. Enjoy :D (Give thanks if this helped you) Thank you!!
[Nexus 5 General] monilchheda:
Out of curiosity can we do multiboot with stock 4.4.4 and Android "L"? Any one tried?
[Nexus 5 General] bcollado:
I am unsure of that especially because of the differences in radios and such. That's why I like this method because it's probably the closest I know how to get to it.
[Nexus 5 General] monilchheda:
Hmm. Thanks
[Nexus 5 General] the.emilio:
My only question to [MENTION=3971668]bcollado[/MENTION] is why not just do fastboot flash recovery command for TWRP?! Faster than using a tool kit.
[Nexus 5 General] simms22:
some people dont know how to do things the right way. many think that root toolkits are easier and faster(when, for any nexus, they are not).
[Nexus 5 General] Elluel:
fastboot flash bootloader bootloader-hammerhead-hhz11k.img

fastboot reboot-bootloader

fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.08.img

fastboot reboot-bootloader

fastboot -w update image-hammerhead-lpv79.zip

there you have "L". lol
[Nexus 5 General] bcollado:
I just figured this guide is aimed towards those who wouldn't know how to do that, obviously it can be done either way, but I assumed if you knew to do it manually, that you could choose to do it that way.
[Nexus 5 General] noodles2224:
Can anyone check to see if they have the Gallery? I had to download QuickPic to view my stuff. But I'm thinking maybe its with Picasa photos app but I removed it from my screen and now I can't find that app.. Can anyone help please. I don't like using 3rd party apps if I already have one working just fine.. Thank you.

Sent from my Nexus 5
[Nexus 5 General] bcollado:
Not the place to ask...but gallery is currently not in the developer preview and might be taken out of android when the release gets finalized, but no one knows. Right now the "Photos" app is included and thats basically the new gallery for now at least
[Nexus 5 General] Elluel:
If they don't know how to do that, why the hell are they flashing the developer preview image? 99% of users are already taking the developer preview as a consumer release, and that is NOT what it is meant for.

If you don't know how to do it - then it's not damn meant for you.
[Nexus 5 General] bcollado:
I hate that attitude....I agree that people need to understand that it's not a consumer release. I 100% agree with that, but that doesn't mean people who don't know how shouldn't be able to check out the new features if they want, just because they don't know how. This is the whole point of this thread...so people can check out the new features on "L" and then go right back to where they were with no issues...please no more flaming on the fact that if people don't know how then they shouldn't, not on this thread anyway
[Nexus 5 General] Elluel:
That's a little bit of contradiction, don't you think?
[Nexus 5 General] bcollado:
Not at all...anyone who wants should be able to view new features, they just have to understand that it's not a final release and that it isn't meant to be used as such. Anyone who doesn't know how to do something and is brave enough to risk it and attempt to, deserves to learn