[ROM][5.0.0][The unnamed Android L SDK port][for MultiROM][06/07/14][v5]

[webdroidmt]

Here you go guyz just flash this zip from recovery(Recover-->Advanced--->Multirom--->List roms--->[select the build]--->flash zip! ) and internet will be all good to go!! :good::good:

All thanks to @gnustomp for pointing it!!

Just hit thanks if it works!!


@500 Internal Server Error
Update-*Rom does not have the NFC.apk neither it has the option to toggle!
*Upon flashing of gapps the TTS gives force close
*Lags


Still small yet significant progress so far!

Thanks for zipping up the lib files, will make it easier for many people. Also, appreciate your overall enthusiasm toward getting "L" running on our device. However, don't you think you might want to click a thanks for gnustomp for finding this?

I know you mentioned him and credited him with the find but unless you used up your 8 thanks for the day, don't you think he deserves a click.

Thanks,
Mike T

 

[500 Internal Server Error]

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

v4:
- Added @gnustomp's Wifi fix - thanks!
- Switched to the Lego Kernel: http://xdaforums.com/showthread.php?t=2664392 this might help F2FS users, since that kernel's commonly used on F2FS ROMs.

I also looked into making this flashable without MultiROM: unfortunately, with the changes, it always tries to flash to the real system partition, even when I want it to flash as a secondary ROM. So I had to Nandroid restore to get my old ROM back. Sigh. I reverted that change.

The remaining serious issues:
- Sound corruption for certain sounds (perhaps with different sample rate?) e.g. the "ding" noise Google Search plays after OK Google is recognized - I already copied over audio_policy.conf, so I dunno what else I need to copy.
- A lot of Play Store applications are marked as incompatiable with device - probably needs a build.prop or a /system/etc/permissions edit
- No Bluetooth and NFC support - I don't have a deodexed Bluetooth.apk and Nfc.apk right now; I might download another ROM and pull them from there.

I would really appreciate if anyone with more porting knowledge can offer advice - this is my first ROM porting project.

I get neverending boot after flashing..but I have to mention I'm on data-f2fs. (Other roms work fine)

Sent using my nexus⁴ running Mahdi 2.7 with Xposed and hells-Core B47 KK

By the way, can someone with a f2fs data partition try to run this? Since the LegoKernel is used for most f2fs ROMs, and MultiROM's trampoline tries to mount /data as f2fs if mounting as ext4 fails, it should boot...

Edit #2: Oh, wow. http://www.androidpolice.com/2014/0...ve-aosp-includes-support-nexus-4-5-7-2013-10/ says Android L source is released? Then I guess this ROM is now obsolete. Ah, well, I'll keep maintaining it until we get a proper Android L port.

 

[RobertsAccount]

Just gonna leave this here.

https://android.googlesource.com/device/asus/grouper/+/l-preview

 

[ironmaskusa]

This means AWESOMENESS!! ??✌

 

[Leraeniesh]

Very exciting. Good to see this available for the 2012 devices.

Sent from my One using XDA Premium 4 mobile app

 

[ironmaskusa]

Yea this ROM is pretty shot. I can't do **** with it now. I tried flashing gapps and the internet fix and it crashes everywhere. But it did boot. I'm sure some one will release an unofficial release of this soon now that the sources have been released! Awesome that you attempted to try this though. Good luck with your future endeavors! ?

 

[Imacellist]

Yea this ROM is pretty shot. I can't do **** with it now. I tried flashing gapps and the internet fix and it crashes everywhere. But it did boot. I'm sure some one will release an unofficial release of this soon now that the sources have been released! Awesome that you attempted to try this though. Good luck with your future endeavors! ?

Works fine if you use multi rom. I didn't have any issues at all once the internet fix was applied. V4 doesn't actually need it since it was built in. You may want to try again.

 

[LucaAN4]

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

v4:
- Added @gnustomp's Wifi fix - thanks!
- Switched to the Lego Kernel: http://xdaforums.com/showthread.php?t=2664392 this might help F2FS users, since that kernel's commonly used on F2FS ROMs.

I also looked into making this flashable without MultiROM: unfortunately, with the changes, it always tries to flash to the real system partition, even when I want it to flash as a secondary ROM. So I had to Nandroid restore to get my old ROM back. Sigh. I reverted that change.

The remaining serious issues:
- Sound corruption for certain sounds (perhaps with different sample rate?) e.g. the "ding" noise Google Search plays after OK Google is recognized - I already copied over audio_policy.conf, so I dunno what else I need to copy.
- A lot of Play Store applications are marked as incompatiable with device - probably needs a build.prop or a /system/etc/permissions edit
- No Bluetooth and NFC support - I don't have a deodexed Bluetooth.apk and Nfc.apk right now; I might download another ROM and pull them from there.

I would really appreciate if anyone with more porting knowledge can offer advice - this is my first ROM porting project.



By the way, can someone with a f2fs data partition try to run this? Since the LegoKernel is used for most f2fs ROMs, and MultiROM's trampoline tries to mount /data as f2fs if mounting as ext4 fails, it should boot...

Edit #2: Oh, wow. http://www.androidpolice.com/2014/0...ve-aosp-includes-support-nexus-4-5-7-2013-10/ says Android L source is released? Then I guess this ROM is now obsolete. Ah, well, I'll keep maintaining it until we get a proper Android L port.

Hey!
This Port is cool and mostly smooth, i would use it as a daily driver, but i've got 1 issue that gets on my nerves. Sometimes a red frame appears at the screensides. It's like strict mode activated, but it isn't. You know how to fix this? I would really appreciate it.

 

[gnustomp]

The android-l sources in AOSP aren't full sources but are only GPL files. Everything that's not GPL is the same as master - so no, you can't compile Android L - yet.

---------- Post added at 03:16 PM ---------- Previous post was at 02:46 PM ----------

Google Play Store app permissions are fixed by copying most things from /system/etc/permissions from the stock ROM, however, don't copy anything related to NFC, because that will cause some apps (notably Settings) to throw a NullPointerException and FC. You should also remove anything that is already in /system/etc/permissions on the port, but you have to make a few edits to `tablet_core_hardware.xml`. The pre-edited file is attached (rename it to .xml).

NOTE THAT THIS MAY BE INTRODUCING MORE BUGS!!! If an app crashes after you did this, but it was working before, tell me what app it is (the package name is helpful) and send (or paste, or whatever) a logcat to me.

This also makes things like Wi-Fi show up in settings.

 

[Maxr1998]

By the way, can someone with a f2fs data partition try to run this? Since the LegoKernel is used for most f2fs ROMs, and MultiROM's trampoline tries to mount /data as f2fs if mounting as ext4 fails, it should boot...

Nope, it doesn't work. Same as before. BTW, I'm on Oxydo kernel with LegoKernel ramdisk.

A few additions: I also installed this on a ext4-formatted USB-stick, but I still get the same issues like on normal storage:

On "Don't Share" Kernel (as proposed by you) it just plays boot animation of primary rom, it doesn't even seem to boot (e.g. USB-stick idle, means light doesn't blink, logcat doesn't connect)
On "Share" Kernel (as presupposed for f2fs and MultiRom * ) it boots with never ending boot animation (shows correct boot animation, USB-stick blinks, logcat is there)

Logs:
http://pastebin.com/V26cgXKu -- Part 1
http://pastebin.com/dPeMgWHt -- Part 2

*
Some things you have to know: (READ THEM)

• All your ROMs must support F2FS so if you want to use "normal" ROMs you have to "share kernel"

Sent using my nexus⁴ running Mahdi 2.7 with Xposed and hells-Core B47 KK

 

[basuraunak]

The android-l sources in AOSP aren't full sources but are only GPL files. Everything that's not GPL is the same as master - so no, you can't compile Android L - yet.

---------- Post added at 03:16 PM ---------- Previous post was at 02:46 PM ----------

Google Play Store app permissions are fixed by copying most things from /system/etc/permissions from the stock ROM, however, don't copy anything related to NFC, because that will cause some apps (notably Settings) to throw a NullPointerException and FC. You should also remove anything that is already in /system/etc/permissions on the port, but you have to make a few edits to `tablet_core_hardware.xml`. The pre-edited file is attached (rename it to .xml).

NOTE THAT THIS MAY BE INTRODUCING MORE BUGS!!! If an app crashes after you did this, but it was working before, tell me what app it is (the package name is helpful) and send (or paste, or whatever) a logcat to me.

This also makes things like Wi-Fi show up in settings.

Shouldn't we should remove the GSM and CDMA from the file as they are not needed by grouper?

Sent from my C2105 using XDA Free mobile app

 

[gnustomp]

Shouldn't we should remove the GSM and CDMA from the file as they are not needed by grouper?

Sent from my C2105 using XDA Free mobile app

In tablet_core_hardware.xml they're there to say you need those files for GSM and CDMA phones, but those files don't exist so it should be fine. They're actually comments, so the system doesn't read them. I believe those two lines are also in the same file in the stock ROM.

 

[lucabi1]

I just tried the v4 and I must say two things:
1- Great job! :good:
2- I found two problems: a red edge all around the screen when an app requires the entire screen or when an error happens; when I try to install an apk downloaded from the web I get an error toast.

 

[klaus27]

The red box is there because it's an sdk build. See if you can change the build type our launch type from ENG to user - maybe in build.prop

If this does not work, add the following two lines in build.prop

persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1

I just tried the v4 and I must say two things:
1- Great job! :good:
2- I found two problems: a red edge all around the screen when an app requires the entire screen or when an error happens; when I try to install an apk downloaded from the web I get an error toast.

 

[lucabi1]

The red box is there because it's an sdk build. See if you can change the build type our launch type from ENG to user - maybe in build.prop

If this does not work, add the following two lines in build.prop

persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1

It works! I changed the string "ro.build.type=en" into "ro.build.type=user" and no more red edges! Thank you @klaus27
A full wipe solved my problem with downloaded apps.

 

[O2Blevel]

Hi guys, I got Wi-Fi working.
The problem is that @500 Internal Server Error forgot to copy a couple of libraries.
The libs needed for WiFi are:

/system/lib/libiprouteutil.so
/system/lib/libnetlink.so

Copy them from the stock ROM.

There are probably a lot more other files that are missing in this ROM, so check if you get an error like

CANNOT LINK EXECUTABLE: could not load library "libiprouteutil.so" needed by "ip"; caused by library "libiprouteutil.so" not found

That tells you what library is missing.

UPDATE: proof (just in case)

shell@grouper:/ $ ping google.com
PING google.com (74.125.237.166) 56(84) bytes of data.
64 bytes from syd01s18-in-f6.1e100.net (74.125.237.166): icmp_seq=1 ttl=56 time=38.5 ms

I've tried v3 with wifi fix and v4 but I don't have any wireless settings in the settings app. How did you enable wifi once you installed the missing libraries?

 

[RobertsAccount]

I've tried v3 with wifi fix and v4 but I don't have any wireless settings in the settings app. How did you enable wifi once you installed the missing libraries?

If you install gapps it should take you through the wifi settings on initial setup.

 

[lucabi1]

I've tried v3 with wifi fix and v4 but I don't have any wireless settings in the settings app. How did you enable wifi once you installed the missing libraries?

You can use the WiFi toggle in the status bar

 

[O2Blevel]

If you install gapps it should take you through the wifi settings on initial setup.

That seems to be my problem, setup crashes for me, don't know why, even though I can flash gapps without any problem.

EDIT: I'm on 4.4.4, anyone else having problems running the ported version?

 

[Imacellist]

That seems to be my problem, setup crashes for me, don't know why, even though I can flash gapps without any problem.

EDIT: I'm on 4.4.4, anyone else having problems running the ported version?

Are you using the correct gapps? Make sure you are using the ones in the OP and not the normal ones you are using.

Sent from my HTC6435LVW using Tapatalk