yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] AndroidInsanity:
So i can just install without needing to wipe anything with multirom?

Just don't wanna lose anything on my current ROM (apps, pics, music)

Sorry for all the questions, just really wanna try this and I am new to multirom.
[Nexus 7 (2013) Android Development] sykopompos:
Yup, you should be good on multirom. Just make sure that you make a nandroid just in case.

I always suggest users keep a backup of important things like pics if they are flashing Roms though
[Nexus 7 (2013) Android Development] AndroidInsanity:
Doesn't work with multirom. It fails then deletes the "incomplete rom".
[Nexus 7 (2013) Android Development] manueltts:
I do use it on multirom, check your download file

Sent from Nexus 7.2 Flo using Tapatalk.
[Nexus 7 (2013) Android Development] AndroidInsanity:
oops hahah, I downloaded the LTE one -_- how embarassing. my bad.
[Nexus 7 (2013) Android Development] mtatq:
when I flash, It said : This is a "flo", and failed, what does it mean ?

I used this file : L-Deb-breadcrumbs-n-Bunnies-5.9.6.zip

Thank you so much
[Nexus 7 (2013) Android Development] poondog:
Cause you flashed deb (3g version) on a flo (WiFi nexus 7)
[Nexus 7 (2013) Android Development] sykopompos:
I am so glad I left those safety checks in there. I had a guy earlier who tried to flash deb on mako because he saw the 9.6 and though it was newer and he had to update
[Nexus 7 (2013) Android Development] poondog:
Should write in caps and underlined man
[Nexus 7 (2013) Android Development] manueltts:
[MENTION=1050103]sykopompos[/MENTION], it seems that the common device name is needed on the files (maybe Nexus2013Wifi for flo, Nexus2013LTE for deb, Nexus4 for mako, Nexus5 for hammerhead). What do you think?
[Nexus 7 (2013) Android Development] sykopompos:
Unfortunately yes
[Nexus 7 (2013) Android Development] idCyber:
no real need for specifics on file names... if you have the device for more than 1 hour, then you know it's codename... I know that my phone is galaxysmtd (SGS I), my tablet is flo (Nexus 7 2013 WiFi), just needs to read carefully the filenames.
[Nexus 7 (2013) Android Development] sykopompos:
Most people do know their device's development name from flashing things like cm or looking at the forum/thread header but you do get the people who get a bit too excited or are new to rooting and flashing and just want to try L
[Nexus 7 (2013) Android Development] AndroidInsanity:
Personally.... I was just tired when I was trying to download the ROM lol.

Although I agree, if your XDA member it's best to know your devices codename.
[Nexus 7 (2013) Android Development] mobilephone01:
I think ordinary device name is the best. Nexus 7 2013 wifi! We don't have any reason to use "flo". What do you think?
[Nexus 7 (2013) Android Development] sykopompos:
It is easier to put in a file name....
[Nexus 7 (2013) Android Development] mobilephone01:
Not much difference. I think
[Nexus 7 (2013) Android Development] sykopompos:
Oh there is, that is why no developer uses the full name and board name is easier plus it keeps it consistent
[Nexus 7 (2013) Android Development] manueltts:
And a sign of respect to our beloved buddies (i.e. devices)
[Nexus 7 (2013) Android Development] mobilephone01:
Oh there is, that is why we should use full name is easy to recognize for user plus it keeps it consistent
[Nexus 7 (2013) Android Development] sykopompos:
But it is supposed to be easier for the developer and is consistent with every other developer
[Nexus 7 (2013) Android Development] mobilephone01:
How much easier?

There is no reason to use code name. How many times developer typing device name? Just thread title and file name. I don't think it's a big job.
[Nexus 7 (2013) Android Development] sykopompos:
Easier when every reference in the code is to the board name and not the marketing name
[Nexus 7 (2013) Android Development] mobilephone01:
Better to change everything. It's the easy way for everyone. I did not know the code name before of course and still I'm confusing the code name.
[Nexus 7 (2013) Android Development] sykopompos:
Tell google to change every code name reference to the marketing name then.

Nexus 7 2013 wifi only = flo

Nexus 7 2013 lte = deb

Nexus 5 = hammerhead

Nexus 4 = mako

Nexus 10 = manta

Nexus 7 2012 WiFi only = grouper

Nexus 7 2012 LTE = tilapia

Galaxy nexus gsm = tuna

Galaxy nexus CDMA = toro

Nexus s = crespo

That covers the nexus devices. Always a fish, whale, shark

Rumored name for next nexus = shamu
[Nexus 7 (2013) Android Development] sykopompos:
Everywhere on XDA, you will see the board name because this is a developer site. You kinda get used to it when you gotta figure out what bacon is, or d2tw or m7, m8 and pyramid and glacier and Odin and all the other names that are completely different from the marketing names
[Nexus 7 (2013) Android Development] mobilephone01:
Sorry. Story went wrong way. They can use flo most of the time but Should use full name for a file name.
[Nexus 7 (2013) Android Development] sykopompos:
Alright. I'll let you do that then. Also spaces don't work well in Linux file systems
[Nexus 7 (2013) Android Development] poondog:
Imo if you don't know the name of your device you shouldn't be flashing anything lol
[Nexus 7 (2013) Android Development] sykopompos:
That's kinda how I feel. Even the big guys like cm, pa and omni is by device name and not marketing name
[Nexus 7 (2013) Android Development] poondog:
^^

dem feels
[Nexus 7 (2013) Android Development] sykopompos:
BTW there is a new flo test build floating around the mako thread with updated preview binaries and matching hal files. Just upgraded mako and hammerhead to the latest google apps and will do flo and deb tomorrow.

I still do most of my development in the mako thread right now since the flo and deb threads aren't that active

You should join us poondog
[Nexus 7 (2013) Android Development] poondog:
What would I be doing and when do I get paid :D
[Nexus 7 (2013) Android Development] sykopompos:
Hanging out and chilling with the rest of us. The n4 thread is very chill and relaxed.

Also I'm wondering myself when do I get paid???? :screwy:
[Nexus 7 (2013) Android Development] bitstra:
[MENTION=1050103]sykopompos[/MENTION],

flo-prop-test-1 clean flashed - nearly perfect! :good:

thanx mate

Edit: [MENTION=1050103]sykopompos[/MENTION]

did some more tests:

flo-prop-test-1 - unfortunately the camera bug is back "Can't connect to camera"
[Nexus 7 (2013) Android Development] poondog:
Haha, I got paid today :D

is this the new build from the mako thread? When's the official L due btw, wasn't it supposed to be September?

L + moto360 = birthday
[Nexus 7 (2013) Android Development] bitstra:
Yes DL via mako thread...
[Nexus 7 (2013) Android Development] sykopompos:
Can I gets paid too???

From what I heard, it isn't supposed to be out till late November
[Nexus 7 (2013) Android Development] dictionary:
You're making me think about fixing the digitizer on my n7 now, lol. If you get the 1+1 working, then I'd have your ROM on three devices. Mmmm. Too bad I couldn't run the fourth with the m7 before I sold it.
[Nexus 7 (2013) Android Development] poondog:
Mate did the music displaying in the music apps get fixed yet? :) Does it work on mako
[Nexus 7 (2013) Android Development] sykopompos:
Yup. Updated google apps
[Nexus 7 (2013) Android Development] poondog:
pls fix thx
[Nexus 7 (2013) Android Development] sykopompos:
Can I say no?
[Nexus 7 (2013) Android Development] poondog:
plz help a n00b :(((((((((((((
[Nexus 7 (2013) Android Development] sykopompos:
You are about as much of a noob as I am then
[Nexus 7 (2013) Android Development] poondog:
we all n00b
[Nexus 7 (2013) Android Development] ANDR01DN00B:
Are we not ;)

Get it? No? OK :/
[Nexus 7 (2013) Android Development] ANDR01DN00B:
OT: my contract is expiring soon and I would like a 2560x1440p device (Note 4, G3, maybe MotoS/NexusX). But, I am not a huge fan of Touchwiz or OptimusUI, and rather get a phone from my carrier on-contract. But if the MotoS/NexusX doesn't end up having a 2560x1440p display, what are the chances of either of those devices getting an optimized Android L ROM soon? Will it be difficult due to the fact that those devices will require a xxxhdpi folder in /res of framework-res.apk and SystemUI for full optimization? Or will it be a fairly easy process?

And I know OT is allowed so don't tell me it isn't ;)
[Nexus 7 (2013) Android Development] sykopompos:
Well since I got a g3, you better believe it will get an optimized L on it :p

The screen size isn't a issue either, google will add support for the size of the screen in aosp
[Nexus 7 (2013) Android Development] ANDR01DN00B:
Oh yeah I forgot you got one!!! I might just get the Note 4 because of its aluminum build and larger body. I like the G3, but i think it is too small and because I work better with and prefer larger phones.

Anyway about this ROM, I have not been able to change Location from High Accuracy to Battery Saving, has this been issued before/been fixed? Oh and is there some app to enable a doubletap to sleep feature our something similar to it?

Thanks
[Nexus 7 (2013) Android Development] sykopompos:
The battery saver for GPS isn't working on any build, it is a preview bug.

For d2tw, most people are using a kernel because apps eat the battery
[Nexus 7 (2013) Android Development] sykopompos:
Flo test gonna be incoming.

If you have a n4 or n5, you are familiar with the slim builds.

All tests are slim builds which mean the non core google apps are ripped out and can be grabbed from the market.

Will update post with the test link.

This is a test on the newer proprietary files and aosp merged in.

Last test was a issue where I broke the camera so it should be working now

https://drive.google.com/file/d/0By0vn8iv_zrVVmZmWmxmLVlfYjg/edit?usp=sharing
[Nexus 7 (2013) Android Development] paztine:
this is the one..

so this is the one your talking about..gonna give it a try..guess need a full wipe,,if I am coming from 5.9.6 ...
[Nexus 7 (2013) Android Development] sykopompos:
You should be good on a dirty flash since I haven't started updating the built in google apps yet
[Nexus 7 (2013) Android Development] paztine:
thanks...

will give that dirty flash a try...
[Nexus 7 (2013) Android Development] sykopompos:
Most of those in there have been proven already as good but I broke the camera in the last test so I went back through redoing the proprietary files in case I missed one or 2
[Nexus 7 (2013) Android Development] paztine:
One Plus One

Hope you can create this awesome rom for ONE PLUS ONE..so I can start my L PREVIEW on my ONE PLUS...

---------- Post added at 08:15 PM ---------- Previous post was at 08:14 PM ----------

still downloading..will report back the result...
[Nexus 7 (2013) Android Development] sykopompos:
I ran into issues before with the display driver along with audio and wifi on the 1+1 which display drivers not matching up was killing it from working (it booted up behind the non working display) on the 1+1 and g3.

I know a bit more about the egl drivers so once I get the current devices squared away, I will be taking another look at them
[Nexus 7 (2013) Android Development] paztine:
good to know..

I havent rooted my ONE PLUS its my DD..because I want something different..no offense to the devs...I want a new UI experience..
[Nexus 7 (2013) Android Development] sykopompos:
Isn't the 1+1 just cm11 with a few tweaks anyways?
[Nexus 7 (2013) Android Development] paztine:
Test 1..zip

Dirty flash from 5.9.6 to test1.zip..Boots up fine..but cant connect to camera..I thought its a slim file..same as your 5.9.6 file size..Maybe needs a clean flash...

---------- Post added at 08:35 PM ---------- Previous post was at 08:31 PM ----------

yes in a way..and less FC...no offense to CM lovers..just stating my experience...
[Nexus 7 (2013) Android Development] manueltts:
Same here! With a clean flash. Smooth and stable, except the camera.
[Nexus 7 (2013) Android Development] paztine:
thanks..

Thanks for the heads up..I was about to clean flash..but decided to flash back to 5.9.6.I dont use camera on my tab..but its good that everything works on your toys...Just my take...
[Nexus 7 (2013) Android Development] sykopompos:
I think I might have uploaded the old one from the first prop test :banghead:
[Nexus 7 (2013) Android Development] sykopompos:
Yup, I uploaded the first prop test again. Reuploading the new one as 2, it is a slim test at 400 mb
[Nexus 7 (2013) Android Development] sykopompos:
alright, let's try this again.

Here is the current test

https://drive.google.com/file/d/0By0vn8iv_zrVaGRLenAzUW9YM2s/edit?usp=sharing
[Nexus 7 (2013) Android Development] manueltts:
Dirty flash booted extremely fast but some other minor bugs... That are not bugs until I try a clean flash, so give me a minute. :)

Edit: clean install as secondary. At first glance: good and fast, with some new problems. Su is not working (need to update binaries but doesn't do it), camera still not connects. That to be short and by now.
[Nexus 7 (2013) Android Development] bitstra:
downloading now - and will test it immediately...:good:

(YOU've got a PM:))
[Nexus 7 (2013) Android Development] sykopompos:
That's permissive not working or the over sized issue popping back up again. Either way neither of those things were changed

Also, stupid camera
[Nexus 7 (2013) Android Development] bitstra:
... tested latest flo-test-2 (≈400 MB) :

- superuser OK

- Camera 'Can't connect to camera' :(

(also 3rd party camera apps like 'Paper Cam')

DAMN CAMERA...

If a logcat would be useful - I can post it...
[Nexus 7 (2013) Android Development] sykopompos:
I'm gonna have to reverse all the proprietary files and aosp hal drivers and merge them in in batches to try to isolate what is breaking the camera
[Nexus 7 (2013) Android Development] bitstra:
If you would post here short instruction how to do that today eveneing, that could become my part. I think I've done that with flo-prop-test-1 by myself. But a small 'howto' would be helpful - and I could do that for us.

(I'm sure - you don't you own a flo till now:silly:)
[Nexus 7 (2013) Android Development] sykopompos:
Well reverting is done on github but once I do that and give you back 5.9.6 in the source, I can group out the files like I did with ramjet for the n5 grouped out in most likely good, bad and so forth as a way to stage them in as to what could be the file that is the issus.

If you are using Linux, the easiest way to work with it is to download the github project and go from there (you might wanna wait till I can revert it so you aren't double downloading)
[Nexus 7 (2013) Android Development] ANDR01DN00B:
Ignore the DPI I just wanted to see how 480 looked on a tablet ??

But why is there not any xxhdpi resources in framework-res or SystemUI? Is it just because it is just a preview and Google is restricting us from seeing L's true colors? Or is there a deep dark secret reason that you guys are going to tell me if you know it anyway?
[Nexus 7 (2013) Android Development] sykopompos:
Definitely a deep dark secret any you shall never know!!!!!
[Nexus 7 (2013) Android Development] ANDR01DN00B:
That is implying that you know... The hunter is now being hunted...
[Nexus 7 (2013) Android Development] sykopompos:
Dun dun DA......
[Nexus 7 (2013) Android Development] bitstra:
Mate, I have a working camera under flo-prop-test-2 :) - after 2 hours of copying/reverting back multiple files PUH...

It wasn#t the sensor stuff - but the camera.flo.so + related camera- and and C2D-stuff in /system/lib

making a detailed list of files I've reverted back to files from L-Flo-bredacrumbs-n-Bunnies-5.9 right now

(post it later - after I triple checked it :) ):good:
[Nexus 7 (2013) Android Development] bitstra:
O.K. - here is the list of reverted files for fixing camera in flo-prop-test-2:

- /lib/hw/camera.flo.so

(this file I've used from 'mod-flo-81c.zip' - all others start with 'Can't connect to camera', also the one from 'L-Flo-breadcrumbs-n-Bunnies-5.9.zip!)

- /lib/libC2D2.so

- /lib/libc2d30-a3xx.so

- /lib/libc2d30.so

- /lib/libc2dcolorconvert.so

- /lib/libcamera_client.so

- /lib/libcamera_metadata.so

- /lib/libcameraservice.so

(these files I've used from ''L-Flo-breadcrumbs-n-Bunnies-5.9.zip'!)

attached zip file contains the werking file-combo (@all, this is not flashable zip!)...
[Nexus 7 (2013) Android Development] bitstra:
the GPS issue with flo-prop-test-2

[MENTION=1050103]sykopompos[/MENTION], and maybe someone else,

I've tried revert all gps related stuff - no success!

The concrete issue is the following:

The basic location service works properly! That means, Google Maps (i.e.) receives correct location data via androids location provider!

So the sub issue was not visible for all of us since prop tests...

But beside the location provider we have normally the ability to read raw NMEA Data from the GPS device...

That worked till 'L-flo-breadcrumbs-n-Bunnies-5.9.6' properly!

can be tested with 'GPS-Status App' from PlayStore and/or with my own 'App for Navilock devices'...

Since flo-prop-test-1 this ability has been gone...

So too in flo-prop-test-2...

Now I'm curious, with which of the prop.-library-change this function was lost.

After trying to revert back all gps-related libs 'n hal I was not able to get the NMEA-GPS-stuff back :(

Any Idea???
[Nexus 7 (2013) Android Development] sykopompos:
You got 4 libloc files, 2 in lib, 2 in /vendor/lib

GPS also goes through the qmux
[Nexus 7 (2013) Android Development] bitstra:
[MENTION=1050103]sykopompos[/MENTION]

... These prop-files were not the bandits:)

Nevermind - after hours of reverting things back one single binary was the trubblemaker for GPS-NMEA support:

/system/bin/rmt_storage

i've used now the rmt_storage from L-Flo-Breadcrums-n-Bunnies-5.9

and the ability for reading raw NMEA-Data from GPS is back again for flo-prop-test-2 !!! :good::laugh:

so now I would say flo-prop-test-2 is good to go... - WORKING CAMERA & FULLY WORKING GPS

Thanx for your patience with me and for your great knowledge and support [MENTION=1050103]sykopompos[/MENTION]
[Nexus 7 (2013) Android Development] NinjaWolf:
Hey, i just bought a used broken 32gb flo tablet off ebay for 30 and fixed it and want to get android l running on it.

Is 5.9.6 stable or should i wait for v6(read the whole thread but cant fixgure out how stable it is)

Thanks for the help.
[Nexus 7 (2013) Android Development] manueltts:
It's. Good to go. Give it a try. Just make sure you won't need apps that are not yet compatible with L (like casting netflix). There is a wide list somewhere; Google will help you with that. Leaving that behind: this is solid and smooth.
[Nexus 7 (2013) Android Development] bitstra:
Update BubbleLauncherL 3.0 + New Extended PowerMenu App

Today I've updatet 'BubbleLauncher-L_For_L-port' to ver 3.0!

New Features:

- Screenshot in Extended PowerMenu module

- Some more L-Themes-Using

Download-Link:

https://www.androidfilehost.com/?fid=23622183712468395 (as zip-file)

https://www.androidfilehost.com/?fid=23622183712468511 (as apk-file)

_______________________________________________________

For those of you, who don't like BubbleLauncher-L

I've made a standalone app 'Extended PowerMenu L ver 1.0'

Feature in powermenu:

- Lock Screen

- Screenshot

- Reboot

- Reboot Recovery

- Reboot Bootloader

- Power Off

for the standalone Extended PowerMenu L app:

after launching the app -> swipe down from Status Bar - a notification for Extended PowerMenu will become visible

Tap onto the notification - The Power Menu will open white and shiny

Download-Link:

https://www.androidfilehost.com/?fid=23622183712468469 (as zip-file)

https://www.androidfilehost.com/?fid=23622183712468510 (as apk-file)

_______________________________________________________
[Nexus 7 (2013) Android Development] sykopompos:
I've been thinking about this a bit. Do you think that would have anything to do with the batter saver mode for location and why we can't set it?

Maybe the kit Kat binary version would allow it?
[Nexus 7 (2013) Android Development] bitstra:
...maybe - Will have a look into that just now. And will see what's possible/impossible...
[Nexus 7 (2013) Android Development] sykopompos:
I was definitely thinking the same thing with it being a network problem, just needed a second opinion from someone with a bit more GPS knowledge
[Nexus 7 (2013) Android Development] manfio:
what is the problem with the camera?

my camera works good, dont have any issue...
[Nexus 7 (2013) Android Development] poondog:
Out of interest, is there APM available for mako or hammerhead?
[Nexus 7 (2013) Android Development] sykopompos:
APM? Advanced power menu?
[Nexus 7 (2013) Android Development] poondog:
Yes sir
[Nexus 7 (2013) Android Development] sykopompos:
[MENTION=4379011]poondog[/MENTION] we thankfully have Mr [MENTION=2981094]bitstra[/MENTION] to thank for that
[Nexus 7 (2013) Android Development] SHABBYLEA:
Is this a DEVO reference?
[Nexus 7 (2013) Android Development] ANDR01DN00B:
No I was making a reference to my username ;)
[Nexus 7 (2013) Android Development] marcocsh:
Bluetooth tethering

Hey mate, thanks for bringing this to our device! Is bluetooth tethering working on this build?
[Nexus 7 (2013) Android Development] sykopompos:
To be honest, I really don't know. I believe it was mentioned that it was working
[Nexus 7 (2013) Android Development] SHABBYLEA:
Put the file onto your Internal Storage

Reboot into Recovery (CWM/TWRP]

"wipe data/factory reset"

"mounts and storage" -> "format system"

"advanced" -> "wipe dalvik cache"

"install zip" -> "install zip from sdcard" -> choose the L-bla-bla-zip and confirm flashing procedure

"wipe cache"

"advanced" -> "wipe dalvik cache"

"reboot into system"

first boot may take up to 10 minutes - be patient

Forgive me if I sound a bit stupid, but if format system, won't the zip be wiped?

Apologies if I have misunderstood the instructions...

Thanks...

---------- Post added at 08:41 PM ---------- Previous post was at 08:31 PM ----------

Oh..I thought it was a riff on "ARE WE NOT MEN", part of a DEVO lyric!

Being a bit to clever for my good I suspect...:silly:
[Nexus 7 (2013) Android Development] manueltts:
No, that file should be inside internal storage.
[Nexus 7 (2013) Android Development] SHABBYLEA:
Ah.…to root of main storage, not in any directory or folder...?
[Nexus 7 (2013) Android Development] manueltts:
It could be in a subfolder inside internal storage. But it's easier to find it in the root folder of the emulated sdcard. This emulated sdcard is inside data/media; which isn't wiped when you do a factory reset: cache/dalvik/data except data/media. If you wipe system none of those are wiped.

This is a great explanation: http://xdaforums.com/showthread.php?p=55228784
[Nexus 7 (2013) Android Development] SHABBYLEA:
Right, got it. Thanks for the help & link...

Cheers,

Shabby.
[Nexus 7 (2013) Android Development] alexm231:
Since xposed won't work, is there any other way to get battery percentage?

Alex
[Nexus 7 (2013) Android Development] marcocsh:
I tried but cannot get it to work.

I paired my Gnex and N7 like I did using Kitkat. Both devices shows tethering active but turns out that I cannot use any internet service, i.e. web sites, g map, g drive, etc. All apps tells me that I have no internet connection.

Am I the only one getting this problem?
[Nexus 7 (2013) Android Development] GatorsUF:
Can this be installed with multi ROM?
[Desire Q&A, Help & Troubleshooting] lecoq3010:
Hi guys,

I have a HTC Desire. My USB port is broken (no money to fix) so cannot connect it to my PC. I have TWRP as recovery, but it wont install zip files.

e:unable to create updater file in /tmp/updater. There is currently no OS loaded. Is there any way i can install CWM at startup like a .bat file or something when i switch on the phone.

Please, please help me. Phones are expensive in South Africa :(

Thank you so much
[Desire Q&A, Help & Troubleshooting] Saf98:
You might have to use an SD card reader to transfer files, so why don't u flash 4ext recovery pb99img.zip file method so u can install a custom rom, are you s off?