[REQ]Dump of the preinstalled rom - LG G Watch R

People are already recieving their units.
Every other wear prior to this one so far has had roms made directly by goog, I dont expect this is any different.
TheManii said:
Android wear runs, well android.
I would like to request that someone that has a wear to dump the rom that is preinstalled on it, and to make note if there it prompts for an ota on first setup.
I don't know how to enable adb on it, but I would expect that it would be available, for the moment merely doing a
Code:
adb pull /system
will be as much as anyone can expect.
In the event it actually supports fastboot, I'd also like to request a
Code:
fastboot get-var all
Click to expand...
Click to collapse
Here's a guide on enabling adb on wear, it's not specific to any one device:
[How-To] Android Wear: Enable Debugging, Take Screenshots, Unlock The Bootloader, And Root The LG G Watch
You won't be able to root it however for the time being, you need a custom recovery specifically for your device.
I don't know if there's an OTA out yet or not, but I would not be surprised if there is/will be one soon.
Please make note of if you got an ota if you upload a dump.

TheManii said:
People are already recieving their units.
Every other wear prior to this one so far has had roms made directly by goog, I dont expect this is any different.
Here's a guide on enabling adb on wear, it's not specific to any one device:
[How-To] Android Wear: Enable Debugging, Take Screenshots, Unlock The Bootloader, And Root The LG G Watch
You won't be able to root it however for the time being, you need a custom recovery specifically for your device.
I don't know if there's an OTA out yet or not, but I would not be surprised if there is/will be one soon.
Please make note of if you got an ota if you upload a dump.
Click to expand...
Click to collapse
Hi ill try and do this later this evening when i get home. I have a lot of meeting so wont be until later so if someone is going to beat me to it go for it!

when i want to pull the system..
command line is giving error: more than one device and emulator..i have managed to link the watch to localhost:4444

doki81 said:
when i want to pull the system..
command line is giving error: more than one device and emulator..i have managed to link the watch to localhost:4444
Click to expand...
Click to collapse
U trying to adb over blue tooth?
im dumping the system now. give me some time to upload
Sent from my GT-I9505 using XDA Premium 4 mobile app
---------- Post added at 06:50 PM ---------- Previous post was at 06:36 PM ----------
system dump
W110_4.4W.2_System_Dump.zip - 206.78 MB

Hawke84 said:
system dump
W110_4.4W.2_System_Dump.zip - 206.78 MB
Click to expand...
Click to collapse
Thanks, did you have any otas before getting this? I assume there is one but I need confirmation.
Also, what is the bootloader version? Most reliable way is to check in fastboot mode.

TheManii said:
Thanks, did you have any otas before getting this? I assume there is one but I need confirmation.
Also, what is the bootloader version? Most reliable way is to check in fastboot mode.
Click to expand...
Click to collapse
yeah had 1 OTA

Hawke84 said:
yeah had 1 OTA
Click to expand...
Click to collapse
Could you check the bootloader version and kernel version?
The kernel version can be found with:
Code:
adb shell cat /proc/version

TheManii said:
Could you check the bootloader version and kernel version?
The kernel version can be found with:
Code:
adb shell cat /proc/version
Click to expand...
Click to collapse
Linux version 3.10.0-g7326b80 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Thu Oct 9 17:43:04 PDT 2014
---------- Post added at 07:19 PM ---------- Previous post was at 07:15 PM ----------
Hawke84 said:
Linux version 3.10.0-g7326b80 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Thu Oct 9 17:43:04 PDT 2014
Click to expand...
Click to collapse
Is it same kernel as original g watch? I'm wondering if we can use the same root exploit
Sent from my GT-I9505 using XDA Premium 4 mobile app

No they're not the same kernel:
android / kernel/msm / android-msm-dory-3.10-kitkat-wear
android / kernel/msm / android-msm-lenok-3.10-kitkat-wear
lenok's kernel is currently newer then sprat's.
I cant tell you what you can do with the differences, I assume it's a matter of waiting for a custom recovery to be ported.
How long ago have you updated your gwar? If it was very recent, could you do an "adb bugreport" and post that?
If it's recent enough it may still have the ota details inside.

TheManii said:
No they're not the same kernel:
android / kernel/msm / android-msm-dory-3.10-kitkat-wear
android / kernel/msm / android-msm-lenok-3.10-kitkat-wear
lenok's kernel is currently newer then sprat's.
I cant tell you what you can do with the differences, I assume it's a matter of waiting for a custom recovery to be ported.
How long ago have you updated your gwar? If it was very recent, could you do an "adb bugreport" and post that?
If it's recent enough it may still have the ota details inside.
Click to expand...
Click to collapse
i was about a week ago, havent read the log yet
http://d-h.st/0hq

Hawke84 said:
i was about a week ago, havent read the log yet
Click to expand...
Click to collapse
Thanks for uploading it, but it's been too long and it's not in there.

Also: android / kernel/msm / android-msm-dory-3.10-kitkat-wear
I had the wrong repo, dory is the gwa and lenok is the gwar.
Sprat is the gear live, the same conclusion is drawn however: lenok is still newer then dory as far as kernels go.

TheManii said:
Also: android / kernel/msm / android-msm-dory-3.10-kitkat-wear
I had the wrong repo, dory is the gwa and lenok is the gwar.
Sprat is the gear live, the same conclusion is drawn however: lenok is still newer then dory as far as kernels go.
Click to expand...
Click to collapse
as far as i can tell (and im not a dev) the toolkit to root the original g watch uses an insecure custom kernel to allow for root access so we need a kernel dev or something good with compiling from source to build for g watch r

Request 4.4W.1 Rom
would be great if someone could manage to pull the original rom the LGWR comes with
the update to 4.4W.2 introduces a nasty bug that no longer updates the time every minute in ambient mode
(someone still running 4.4W.1 and able to confirm the bug isn't there?)
I learned about this too late and immediately updated my watch on arrival

I still need a dump of KIW52H if anyone still has an unupdated gwar

Cool, dev talk. Well here is my progress. I used the pulled boot.img someone posted here amd I made it insecure and I compiled the insecure boot.img. i am calling it a night but will work on it more this week when I have more time. Although it looks promising.
I also have looked at the oroginal lg g watch tweaks made and think i know how to boost the vibration setting on our device.

Related

[DEV][4.0.7]Huawei USB Dongles.

[UPDATE]2012-08-06 This is not the only way of getting Dongle's working on Android, If widgets are your thing and you doing feel confident working with system files etc then you may be better served using the ppp widget form draisberghof.de, these are the folks who piratically wrote the book on getting dongles working on linux and by extension android.
[UPDATE]2012-08-06 The source to libhuaweigeneric-ril ( github ) has been updated to include fixes made by omegaRed7 - This massively improves the fault tolerance upon RIL Startup, Tests were carried out on the E173s-1 but it should be beneficial to all modems ( I hope ).
[UPDATE]2012-07-28 As the Rom Version is quite old and it doesn't really require it's own rom I've extracted the files required to implement this functionality - Download Here, The Archive contains a README file with installation instructions
IMPORTANT - pppd permission need changing to 6755 also change to ownership to the root account ( Thanks to __DS__ ). you can do this through adb or terminal emulator
Code:
adb shell chown 0:0 /system/bin/pppd
adb shell chmod 6755 /system/bin/pppd
for this to function
[UPDATE]2012-06-25 Added Forked libhuaweigeneric-ril to Github Repo this includes all the changes I've made - Check This Post For Details
[UPDATE]2012-06-23 Added Github Repo - Check This Post For Details
[UPDATE]2012-06-16 THE DOWNLOAD LINK HAS BEEN UPDATED AS THE FILES IN /etc/system/usb_modeswitch WHERE NAMED INCORRECTLY[/UPDATE]
Hi Folks - This post is going to change fairly often, there is still more info to add, I just got bored with typing for now
The Sales Pitch
This rom aims to provides the same "hands free" approach offered by the Archos 3G Key and extends this functionality to Huawei Branded USB Modems.
Introduction
Here is a custom rom I've currently been hacking away at, if feels like I've had it under wraps for months.
That being the case. I'd like to thking on to enable Huawei USB Modems - This is still a WORK IN PROGRESS but It feels like i've been keeping it under wraps for months, So it's time to throw it out there for further testing. So Dongles at the Ready! It could get a little hacky
WARNING
The Full Size USB Slot has been known to fail from moderate use. As such I would recommend using an USB extensions cable for connecting devices.
VERY IMPORTANT NOTES - PLEASE READ
1. This is definitely not an every day use rom on any other device this woud have been deployed as a recovery flashable update. The reasoning behind the rom deployment is it's only one file to copy and youi're ready to go. It is also a tedious task to manually go through (especially on the 100th time
2. Please don't ask a me if a certain device will work or not. It is not helpful on a number of levels,
a) I simply don't know - I don't own the model in question. Further more you can figure it out yourself.
b) The Chances are that you could probably find out the answer without leaving the comfort of xda - The libhuaweigeneric-ril has been passed around xda like a <Insert Well Used Analogy Here> so a quick search of xda may turn up something useful to reassure you.
c) In reality though we are not going to know if your dongle is working until you "Try It Yourself".
3. if you find your device doesn't work then you need to gather all the relevant information to help get a feel of what's going on; See Below
SUPPORTED DEVICES
The theoretical list of supportted devices come from those devices supportted by usb_wwan and option kernelp drivers.
IMPORTANT NOTES - WHAT YOU NEED TO KNOW
In a perfect world you can download/flash the attached update file. Reload your SDE, Plug a USB 3G Dongle and have It connect and go about you day .
This is the ultimate goal and currently what happens on my own device
TROUBLESHOOTING
There's about a 25% based on my current test this won't happen. There are 2 main ways your connection attempt can fail.
1. The UsbStick has not switched to modem mode
2. The ppp connection script failed
Either Way it would be highly useful post the list of system properties, outputs of dmesg and also a full logcat aswell as the vendor/product id from lsusb,
some like this throught the adb
Code:
adb shell getprops
adb shell lsusb
adb shell dmesg
adb logcat -b radio -b system -b main -b events
Please have a glance over it before posting as It may contain information that you would not want others to see!
ROM DETAILS
Android Version: 4.0.3
Archos Version: SDE 4.06
Removed : Nothing
ADDITIONS
init.dongle.rc - initialization script, I wanted to avoid "polluting" any other init file too much
/lib/modules/usb_wwan.ko and /lib/modules/option.ko - USB Drivers for GSM modems
/system/lib/libhuaweigeneric-ril.so - A slightly tweaked version of DerArtem original huaweigeneric-ril
/system/etc/usb_modeswitch - the latest version of the usb-modeswitch-data
/etc/ppp - Added separate gprs scripts to retain compatibility with the Archos datakey
/system/bin/hotplugd - A new native android service; Manages Modeswitching and connection initialization for any Usb Device which has a valid configuration file present.
DOWNLOAD
3G Modem Redist Pack - For use with newer roms
Hotfile - archos.ext4.update.
INSTALL
Unpack zip and copy unpacked update file to the device
Code:
adb push archos.ext4.update /mnt/storage
restart device in sde mode
script should update automatically
KNOWN ISSUES
"3G Stick Connected" Icon remains in notification list after device disconnection.
pppd needs to be executed with elevated privileges.
pppd is not exiting correctly on some occasions and cause reconnection issues when using multiple sticks.
Thanks go to surdu_petru for the base sde, derAtem for his original work on the libhuaweigeneric-ril.so and pretty much every developer who has worked on these dongles with android, I think I've read every thread on XDA regarding this subject
Hi!
Thanks trevd!
I do not have this USB modem ....but you did a good job for those who have this modem ! Good luck...
i have a Huawei E160E
It is possible to add this modle on your rom ?
---------- Post added at 06:46 PM ---------- Previous post was at 06:23 PM ----------
For the buzz in FRANCE (and in the World :-= )
http://www.jbmm.fr/?p=28280
cajl said:
i have a Huawei E160E
It is possible to add this modle on your rom ?
Click to expand...
Click to collapse
Is this a new model ( released this year )? It may already be in there, The easiest thing to do is plug it in.
If you install this app you can find out what the product_id is and then we can find out for sure.
Thanks
no released in 2009
Device Class: Use class information in the Interface Descriptors (0x0)
Vendor ID: 12d1
Vendor Name: Huawei Technologies Co., Ltd.
Product ID: 03eb
Hi trevd.
Thanks for the work.
Before installing your rom, I'd like to know if my Huawei K3565 is or will be supported.
I can't remember when it was released, but it not a new one ; may be 2009 or 2010.
Rackham666 said:
Hi trevd.
Thanks for the work.
Before installing your rom, I'd like to know if my Huawei K3565 is or will be supported.
I can't remember when it was released, but it not a new one ; may be 2009 or 2010.
Click to expand...
Click to collapse
Hi Rackham666
I'd refer back to my first post, I've tried to make it a little more clear what this "rom" exactly is, more a testing ground, my apologises if that wasn't very clear at first glance, So to switch this query right back at you.
After installing my rom, I'd like to know if your Huawei K3565 is supported?.
For my usn dongle , is it ok for you ?
Okay.
I'll try your additions manually when [email protected] V3 will be released by Petru.
Get The Code
Hi Folks.
I've started a github repo if anyone wants to hack on this stuff.... It only contains the code for the hotplug service at the moment but I will obviously add more when I get chance and apply all the proper GPL licenses to it.
A personal word of note : C is not my first language by any stretch ( although it is fast becoming the case ) so If It causes any memory leaks or starts nuclear war I can't be held responsible, however if there is any noob coding errors in there then I'm ready to learn off those more knowledgeable than I. I have a feeling we have some hardcore developers lurking in Archos Development community
Equally If anyone has any fixes drop me a pm and I'll sort commit access on the repo or post them right here in the thread,
The code can be found here https://github.com/trevd
Hi Folks, Me Again!
Just to let you guys know I've added a forked libhuaweigeneric-ril to my github ( https://github.com/trevd )
It includes the changes I made to enable it to work the Archos.
You'll want to clone the ics branch if you want to compile yourself.
cajl said:
For my usn dongle , is it ok for you ?
Click to expand...
Click to collapse
???
I'm not sure I understand what you mean.... can you explain a little more
Thanks
Hi, I'm sorry if I'm bothering you but I've done the steps for installing this but when I get to sde menu nothing happens. You said script should install the update automatically but nothing happens. Is there something else I have to do?
Sorry again and thank you for your work
Sent from my ARCHOS 101G9 using xda premium
alahkel said:
Hi, I'm sorry if I'm bothering you but I've done the steps for installing this but when I get to sde menu nothing happens. You said script should install the update automatically but nothing happens. Is there something else I have to do?
Sorry again and thank you for your work
Sent from my ARCHOS 101G9 using xda premium
Click to expand...
Click to collapse
Hi Alahkel
You're not bothering me .... DO I really sound/come across as that grumpy/angry in my first post.... sometimes I get cranky when I don't get enough sleep.... too much time looking at code.... :laugh:
Thanks for having a go, Are you using the official SDE? and have you got a working SDE Rom already installed?
For now I would forget about the rom image and bear with me, I'm working on an installer APK which will probably better help with testing, I'll also put the manual installation method up for those who want to get dirty with adb.
Hi, i succesfully installed your build then, btw running unoff sde. I have a huawei 170something, I don't remember the model, but it's working great with no problems, but using a otg cable only. I didn't get it to work using the big usb slot
Sent from my ARCHOS 101G9 using xda premium
alahkel said:
Hi, i succesfully installed your build then, btw running unoff sde. I have a huawei 170something, I don't remember the model, but it's working great with no problems, but using a otg cable only. I didn't get it to work using the big usb slot
Sent from my ARCHOS 101G9 using xda premium
Click to expand...
Click to collapse
That's great news Interesting that you couldn't/haven't got it working on the full size port... It should function the same as the official Archos Stick, You need to switch on the 3G Stick in the settings and the full size slot should "Just Work". I may have missed that little detail out
If that doesn't work your full size slot is maybe broken A not uncommon issue it seems. unfortunately.
Out of interest what network are you on?
I'm just working on the installer now so you won't be stuck with old archos versions.
trevd said:
That's great news Interesting that you couldn't/haven't got it working on the full size port... It should function the same as the official Archos Stick, You need to switch on the 3G Stick in the settings and the full size slot should "Just Work". I may have missed that little detail out
If that doesn't work your full size slot is maybe broken A not uncommon issue it seems. unfortunately.
Out of interest what network are you on?
I'm just working on the installer now so you won't be stuck with old archos versions.
Click to expand...
Click to collapse
Hi, thx for answering. Well of course I turn on the 3g key in settings for big-size usb and my huawei 3gkey is on indeed (led on key) but the tab doesn't recognize that o.o I'm on tim (italy ) Thank you
Sent from my ARCHOS 101G9 using xda premium
Hi trevd,
i'm guessing this won't work on CM9 by JackpotClavin, or would it? If yes, would i install it the same way as described?
Thanks in advance!
Edit: Sorry i'm obviously still running in 1st gear in the morning... There's no 3G support in the CM9 port so there's no way this would just "work"...
Edit2: And confirmation that i need more coffee: Saw your post in CM9 thread about the successful connection with Archos' 3G stick and a Huawei 3G stick, but only through the browser... Any progress on fixing things so the ppp connection is fully usable by other apps & services?
Hi, trevd!
how to launch the modem on a firmware 4.0.7?
I copy these files from your firmware
init.dongle.rc - initialization script, I wanted to avoid "polluting" any other init file too much
/lib/modules/usb_wwan.ko and /lib/modules/option.ko - USB Drivers for GSM modems
/system/lib/libhuaweigeneric-ril.so - A slightly tweaked version of DerArtem original huaweigeneric-ril
/system/etc/usb_modeswitch - the latest version of the usb-modeswitch-data
/etc/ppp - Added separate gprs scripts to retain compatibility with the Archos datakey
/system/bin/hotplugd - A new native android service; Manages Modeswitching and connection initialization for any Usb Device which has a valid configuration file present.
Click to expand...
Click to collapse
I change the init.rc file for init.dongle.rc start
but the Huawei E1550 modem doesn't work
what it is necessary to change still?
Thanks!
=========================
sorry, everything earned, it was necessary to update a modem firmware
Hi deman05
You were nearly there, init.dongle.rc is imported on the very first line of init.rc so you need both files.
You shouldn't have to do anything with the modem firmware as usb_modeswitch will handle turning the modem.
The files required are.
init.rc
init.dongle.rc
/lib/modules/usb_wwan.ko
/lib/modules/option.ko
/system/lib/libhuaweigeneric-ril.so
/system/bin/hotplugd
Also you need the full contents of the following directories
/system/etc/usb_modeswitch
/system/etc/ppp
/system/etc/chatscripts
I've attached the latest versions to this post (hopefully I've not missed anything), you will need to change the permissions on /system/bin/pppd.
chmod 6755 pppd
[EDIT] I did miss something, please see the first post for the correct download link.
The new version also handles a cold boot ( modem plugged in on startup ) scenario.
If you are still having issues please refer to the troubleshooting section in my original post
Thanks

Android AOSP 4.3 Compiled for Tablet Z (SGP311)

Since everyone always loves MOAR VERSION NUMBAH...
Android 4.3 for the Xperia Tablet Z (SGP311). With a BIG shout out to Sony Mobile for hosting their own git repository for their devices - https://github.com/sonyxperiadev/device-sony-sgp321
This is compiled from AOSP, and has nothing done beyond that. Simply added the Sony repo to Android 4.3 AOSP, and built. As per the Sony AOSP releases, this does not have functional binary parts. This is not functional for practical use.
Working:
Boots
Not Working:
Wifi
Bluetooth
In light of this not being a working build, I will not post it as a zip, but as fastboot flashable images. Unlocked bootloader only. C6603 was used to test, other models entirely at your risk (ie. don't bother).
Links:
All files needed are in
http://goo.im/devs/pulser/TabletZSGP311/4.3AOSP
and will appear there shortly (upload done, it's still propogating)
This is for the SGP311 Pollux_WINDY device - the 16 GB WiFi-Only model. Don't try it on pollux with LTE, it won't boot. Might work on 32 GB wifi only model, but not tested or sure
Feel free to mirror, share, modify, edit, tweak, fix, etc etc etc. I am not like certain individuals who go ZOMG NO MIRRORS PLEASE... Go on, mirror, make a torrent if you want, and share it if anyone actually cares about this It's really not that good, but hey...
To install:
fastboot flash boot boot.img
fastboot flash system system.img
Build instructions to replicate :
Get android 4.3 sources.
Get sony tablet Z information on repositories and add to local_manifests for 4.3
Get latest v3 blobs for phone and tablet Z
Put them into vendor/sony/
Repo sync
Make
Thanks, @pulser_g2. This is a very necessary and welcome first step towards further development.
And with official v4.2.2 on its way, things should get busier around here. :good:
Great work man THX. Can you make also a build for SGP321 ? I dont have ubuntu installed so i cant compile atm.
m3dd0g said:
Great work man THX. Can you make also a build for SGP321 ? I dont have ubuntu installed so i cant compile atm.
Click to expand...
Click to collapse
I can't test it, so can't be sure it works or anything. If that is the 32 GB model of the pollux_windy, this build should work fine. If it's the pollux (with LTE), then I have no intention to make builds for it, since I have no idea about the device, and I don't just post untested junk
pulser_g2 said:
I can't test it, so can't be sure it works or anything. If that is the 32 GB model of the pollux_windy, this build should work fine. If it's the pollux (with LTE), then I have no intention to make builds for it, since I have no idea about the device, and I don't just post untested junk
Click to expand...
Click to collapse
I have pollux LTE and i can test when you like...
Shanliang- said:
Thanks, @pulser_g2. This is a very necessary and welcome first step towards further development.
And with official v4.2.2 on its way, things should get busier around here. :good:
Click to expand...
Click to collapse
do we have confirmation when this is?
nycbjr said:
do we have confirmation when this is?
Click to expand...
Click to collapse
In early August 4.2.2 should start rolling out, according to XperiaBlog and a tweet from SonyDevs.
Shanliang- said:
In early August 4.2.2 should start rolling out, according to XperiaBlog and a tweet from SonyDevs.
Click to expand...
Click to collapse
thanks we need that update to get working gps on wifi only tabs (I still hate calling it pollux_windy, what a dumb name).
---------- Post added at 04:29 PM ---------- Previous post was at 04:27 PM ----------
pulser_g2 said:
Since everyone always loves MOAR VERSION NUMBAH...
Android 4.3 for the Xperia Tablet Z (SGP311). With a BIG shout out to Sony Mobile for hosting their own git repository for their devices - https://github.com/sonyxperiadev/device-sony-sgp321
This is compiled from AOSP, and has nothing done beyond that. Simply added the Sony repo to Android 4.3 AOSP, and built. As per the Sony AOSP releases, this does not have functional binary parts. This is not functional for practical use.
Working:
Boots
Not Working:
Wifi
Bluetooth
In light of this not being a working build, I will not post it as a zip, but as fastboot flashable images. Unlocked bootloader only. C6603 was used to test, other models entirely at your risk (ie. don't bother).
Links:
All files needed are in
http://goo.im/devs/pulser/TabletZSGP311/4.3AOSP
and will appear there shortly (upload done, it's still propogating)
This is for the SGP311 Pollux_WINDY device - the 16 GB WiFi-Only model. Don't try it on pollux with LTE, it won't boot. Might work on 32 GB wifi only model, but not tested or sure
Feel free to mirror, share, modify, edit, tweak, fix, etc etc etc. I am not like certain individuals who go ZOMG NO MIRRORS PLEASE... Go on, mirror, make a torrent if you want, and share it if anyone actually cares about this It's really not that good, but hey...
To install:
fastboot flash boot boot.img
fastboot flash system system.img
Build instructions to replicate :
Get android 4.3 sources.
Get sony tablet Z information on repositories and add to local_manifests for 4.3
Get latest v3 blobs for phone and tablet Z
Put them into vendor/sony/
Repo sync
Make
Click to expand...
Click to collapse
Hey if you want some help with porting I don't mind lending some assistance, I was going to start on a 4.3 port tonight to find the bugs and get them fixed prior to baked/cm going 4.3 (it takes some time to merge our stuff into a new aosp release)
Sorry for my ignorance but I just got my tablet Z (312)
does this work on the 312? I'm seeing that there is an lte version and 2 wifi versions. Is the only diff between the 2 wifi versions the storage size and do they typically use the same firmware?
nycbjr said:
thanks we need that update to get working gps on wifi only tabs (I still hate calling it pollux_windy, what a dumb name).
---------- Post added at 04:29 PM ---------- Previous post was at 04:27 PM ----------
Hey if you want some help with porting I don't mind lending some assistance, I was going to start on a 4.3 port tonight to find the bugs and get them fixed prior to baked/cm going 4.3 (it takes some time to merge our stuff into a new aosp release)
Click to expand...
Click to collapse
Sure, I just worked off the stuff on sony's github, I need to look at getting more blobs in and fixing stuff now.
Thank you Thank you Thank you
Can't wait for MOAR
Hi All,
Did someone manage to get Wi-Fi and Bluetooth working? And GPS, if there was an issue?
Yes..if u r planning on build for yourself at least...the kernel modules weren't included in the image
Sent from my XT1053 using xda app-developers app
skiwong20 said:
Yes..if u r planning on build for yourself at least...the kernel modules weren't included in the image
Sent from my XT1053 using xda app-developers app
Click to expand...
Click to collapse
Got it, thanks! I don't have Ubuntu, so first will look if I can find it compiled somewhere, then will try to do that myself if wont.

About Android M Source

i noticed that a lot of projects on android.googlesource.com already have the android-m tag, including
plataform/system/core
plataform/build
plataform/frameworks/base
so i think if these non gpl projects are updated with M code, is the source code fully complete? can anyone check if we can already update and build M roms?
I pulled the source via repo, but I haven't got around to a build yet.
Gene Poole said:
I pulled the source via repo, but I haven't got around to a build yet.
Click to expand...
Click to collapse
Would you be able to build roms off of M source? Is it enough source or is it better to wait for new update and factory images? Since the bootloader and radio is the same as that of 5.1.1 shouldn't gapps work?
opssemnik said:
i noticed that a lot of projects on android.googlesource.com already have the android-m tag, including
plataform/system/core
plataform/build
plataform/frameworks/base
so i think if these non gpl projects are updated with M code, is the source code fully complete? can anyone check if we can already update and build M roms?
Click to expand...
Click to collapse
I couldn't get it to build (could be an issue on my side, tho). So I guess it's better to wait for the official announcement before building.
F4uzan said:
I couldn't get it to build (could be an issue on my side, tho). So I guess it's better to wait for the official announcement before building.
Click to expand...
Click to collapse
ok thanks, thanks to my "great" internet (10mbps) i didnt want to loose a full day just syncing
cell2011 said:
Would you be able to build roms off of M source? Is it enough source or is it better to wait for new update and factory images? Since the bootloader and radio is the same as that of 5.1.1 shouldn't gapps work?
Click to expand...
Click to collapse
gapps relly on the system framework (sdk), radio and bootloader rely on nothing, they control the device in a really low level state, in fact the bootloader is the lowest level, since it starts the kernel.
Sometimes radios/bootloader causes issuses depending on the combination but thats because of the blobs system wise, not because of the os version.
And gapps were updated on M
opssemnik said:
ok thanks, thanks to my "great" internet (10mbps) i didnt want to loose a full day just syncing
Click to expand...
Click to collapse
So my whole day sacrifice is worth it then (I synced for like, a day or two).
Anyway, I've seen some component gets android-m-preview tag. Google might be pushing it real soon.
F4uzan said:
So my whole day sacrifice is worth it then (I synced for like, a day or two).
Anyway, I've seen some component gets android-m-preview tag. Google might be pushing it real soon.
Click to expand...
Click to collapse
Does anyone happen to see what android ver this will be? 5.2?
cell2011 said:
Does anyone happen to see what android ver this will be? 5.2?
Click to expand...
Click to collapse
Nah, just m-preview. It's just like L, the development tag is l-preview.
F4uzan said:
Nah, just m-preview. It's just like L, the development tag is l-preview.
Click to expand...
Click to collapse
M preview is 5.1.x for sure. Look at the SDK number : 22, like Android 5.1
I'm almost sure you can build Android M from AOSP, and thats why :
I know the difference between Android 5.1.1 and M is very little, just a few adds, i seen somewhere, speaking of less than 20MB of changed files.. So, try to sync a repo with Android 5.1.1 AOSP, and add the M commits and try to build, to see.
If it builds for Nexus 5, so i can be built for any other device supported by AOSP 5.1.1.
dekefake said:
M preview is 5.1.x for sure. Look at the SDK number : 22, like Android 5.1
I'm almost sure you can build Android M from AOSP, and thats why :
I know the difference between Android 5.1.1 and M is very little, just a few adds, i seen somewhere, speaking of less than 20MB of changed files.. So, try to sync a repo with Android 5.1.1 AOSP, and add the M commits and try to build, to see.
If it builds for Nexus 5, so i can be built for any other device supported by AOSP 5.1.1.
Click to expand...
Click to collapse
Thanks for pointing out ! I totally missed the point that the SDK version is still 22.
I'll try rebuilding M again, the fault could be on my side.
So will this be a build off of 5.1.1 and M if it can be done?
---------- Post added at 06:34 AM ---------- Previous post was at 06:20 AM ----------
This is what member defconoi says about doing a port for the N4. All that needs to be done is to take the nexus 5 image and replace the binaries with the mako binaries preview and then use the nexus 4 m kernel. That's what I did when porting L. I don't know if this can be of any help pertaining to our N5
cell2011 said:
So will this be a build off of 5.1.1 and M if it can be done?
---------- Post added at 06:34 AM ---------- Previous post was at 06:20 AM ----------
This is what member defconoi says about doing a port for the N4. All that needs to be done is to take the nexus 5 image and replace the binaries with the mako binaries preview and then use the nexus 4 m kernel. That's what I did when porting L. I don't know if this can be of any help pertaining to our N5
Click to expand...
Click to collapse
just remember, the n4 dosen´t have an updated kernel source tree with M tag, just the binary, so you guys will need to update the ramdisk for M
opssemnik said:
just remember, the n4 dosen´t have an updated kernel source tree with M tag, just the binary, so you guys will need to update the ramdisk for M
Click to expand...
Click to collapse
Are you working on a build for our N5? Someone on android development has a flashable stock of M deodexed version coming soon its not out yet but the post is
cell2011 said:
Are you working on a build for our N5? Someone on android development has a flashable stock of M deodexed version coming soon its not out yet but the post is
Click to expand...
Click to collapse
im just thinkering with it, nothing for public release.
however you guys can use ext4 image unpacker to work directly with the factory images
http://i.imgur.com/T9SCUSR.png
cell2011 said:
So will this be a build off of 5.1.1 and M if it can be done?
Click to expand...
Click to collapse
I think a combo build with 5.1.1 - M is possible, adding M commits to a 5.1.1 source code, and then, try to build.

[ROM][AOSP 6.0.1_r10]AOSP MM-MR1-RELEASE branch by khaon

Hello everyone,
I have successfully built a package for this device. While the factory images is android-6.0.1_r5, this package features android-6.0.1_r10 along with the optimization flags I use for my other devices.
Instructions:
You need to get a custom recovery, this recovery should work
Boot into twrp
flash the package
optional: factory reset.
I haven't tested this as I am at work currently, so if anyone want to try before I get home do it
LINK​
XDA:DevDB Information
AOSP for Pixel C, ROM for the Google Pixel C
Contributors
Khaon, Namastaz
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Alpha
Beta Release Date: 2016-01-12
Created 2016-01-12
Last Updated 2016-01-12
Sweet! Does this have root integrated, by chance?
oRAirwolf said:
Sweet! Does this have root integrated, by chance?
Click to expand...
Click to collapse
No it doesn't. I could tho, I will see how thing evolves. I had my nexus 10 ramdisk patched for SuperSU. But I think now the flashing package cheks your partitions.
Guys just a reminder: don't flash SuperSU ZIP directly. That goes for stock as well as builds like khaon's (just a heads up), but rather one of the existing root options. Flashing a ZIP that tries to modify the kernel, like SuperSU systemless will fail on the Pixel C and might semi-brick your tablet.
cheep5k8 said:
Guys just a reminder: don't flash SuperSU ZIP directly. That goes for stock as well as builds like khaon's (just a heads up), but rather one of the existing root options. Flashing a ZIP that tries to modify the kernel, like SuperSU systemless will fail on the Pixel C and might semi-brick your tablet.
Click to expand...
Click to collapse
I read somewhere you were saying that the boot image is chromeos alike. Could you link me some source-code so I can see and understand the differences and how chromeos bootimage are built ? I looked at the chromeos's sources but i couldnt figure out where to look at.
Basically the kernel image is a depthcharge (the bootloader) payload that contains the Android kernel which then boots Android.
Depthcharge (bootloader source code with fastboot code): https://chromium.googlesource.com/chromiumos/platform/depthcharge/
Other relevant project there is also vboot_reference.
---------- Post added at 11:49 AM ---------- Previous post was at 11:37 AM ----------
It's not just ChromeOS-like... up to the point where the Android kernel boots Android it's completely like on a Chromebook.
But, sourse code?
So is this using the stock boot image?
Sorry for the late reply...
Martin_Devil said:
But, sourse code?
Click to expand...
Click to collapse
Ewww, I am using this android revision
This tag points to the marshmallow-mr1-release.
There are no sources as it was built with the default sources, however, this was the build platform
bill3508 said:
So is this using the stock boot image?
Click to expand...
Click to collapse
Yes it is using the stock boot image.
Thank you! Could someone please upload the build.prop file? TIA!
Thanks a ton man. I've heard this device is more difficult than other devices to build for. When my type C cables and adapters show up tomorrow I will be unlocking the bootloader, flashing TWRP, nand backup, and then I'm going to try your ROM and then the kernel that's available. So it's going to be a good day .
Sjflowerhorn said:
Thanks a ton man. I've heard this device is more difficult than other devices to build for. When my type C cables and adapters show up tomorrow I will be unlocking the bootloader, flashing TWRP, nand backup, and then I'm going to try your ROM and then the kernel that's available. So it's going to be a good day .
Click to expand...
Click to collapse
You may just want to root the stock ROM. This ROM has not been updated to the new base, which has fixes for the touchscreen issues.

Android N preview supposedly being released March 9th 2016?

http://www.theverge.com/2016/3/9/11185872/android-n-developer-preview-features-report
The first preview build of Android N will be released to the public today with new features including a native split-screen mode, according to a report from 9to5Google. Citing an article from Ars Technica that was pulled after publication, 9to5Google says that the preview version of Android N includes a redesigned notification panel (with notifications that span the full width of the screen, and an edit button for quick changes), and improvements to the operating system's Doze feature, which will reportedly save battery whenever the screen turns off.
THERE'S ALSO A 'PICTURE IN PICTURE' MODE REPORTEDLY COMING
The biggest addition though, seems to be a new split-screen mode for multitasking. This reportedly works on both phones and tablets, and, like other features included in the preview, will be given to developers to test before it's released to the public later this year. 9to5Google says that Ars Technica also reported the existence of a new "picture in picture" mode which sounds similar to that in iOS 9, letting users shrink windows to a corner of their screen while browsing other apps.
The original Ars story also reportedly said that the preview will be available for the Nexus 6P, Nexus 5X, Nexus 6, Pixel C, Nexus 9, Nexus Player, and the General Mobile 4G. Google is also said to be launching a new "Android Beta Program." All of this information is extremely provisional at the moment, but if the Ars Technica report is true, we can expect to hear more about Android N — and its new features — some time soon.
I would be surprised if it actually releases today, but one can hope!!
It's out! http://storage.googleapis.com/androiddevelopers/shareables/preview/shamu-npc56p-preview-54b13c67.tgz
Currently unlocked bootloader and running twrp 3.0
That being said how would I go about installing this image? The same way as the other images? Also, if I do this, will I be able to revert back?
Developer preview? It's still functional as a phone?
Awesome, thanks! I just downloaded the Shamu preview from http://developer.android.com/preview/download.html. Has anyone extracted and installed the images on their rooted 6.0.1? I'd rather not be the first, lol!
Official Release Page:
https://developer.android.com/preview/index.html
Having an OTA of the N preview is Awesome! I want to try it as soon as the site is availble, but I'm not sure how friendly the N preview will be for project fi this early. anyone else on Fi going to try the preview?
Flashable zip or it isn't true
matthew2926 said:
Flashable zip or it isn't true
Click to expand...
Click to collapse
give some time someone will make one
Cobra11Murderer said:
give some time someone will make one
Click to expand...
Click to collapse
Haha yea, I just wish I knew how to make one myself...oh well
I wasn't expecting that, well safe to say this will be last of the preview for us. Safe to say folks with the OG Nex5 won't get android N
---------- Post added at 08:11 PM ---------- Previous post was at 08:11 PM ----------
Any changes to the launcher?
This flashes just like a regular Nexus image right ? aka unzip, fastboot, etc, etc..............
md1008 said:
I wasn't expecting that, well safe to say this will be last of the preview for us. Safe to say folks with the OG Nex5 won't get android N
---------- Post added at 08:11 PM ---------- Previous post was at 08:11 PM ----------
Any changes to the launcher?
Click to expand...
Click to collapse
eh probably but it can be ported over just like any other rom
mikeprius said:
This flashes just like a regular Nexus image right ? aka unzip, fastboot, etc, etc..............
Click to expand...
Click to collapse
Yup, the usual img`s flashed in fastboot
mikeprius said:
This flashes just like a regular Nexus image right ? aka unzip, fastboot, etc, etc..............
Click to expand...
Click to collapse
In suggest wait for sometime and someone will surely give flashable zip... Then give a try.... Rest your own wish.....
Sent from my Nexus 6 using Tapatalk
Probably the coolest features, for me anyway, is built-in options to calibrate the display color (in System UI Tuner) AND change the DPI (in Display settings). I'm not sure if these will make it to the final build, but I really do hope so.
PS: you need to sign up for the android beta program to actually receive OTA updates https://g.co/androidbeta
as stated here: http://developer.android.com/preview/overview.html
deeplyyoung said:
In suggest wait for sometime and someone will surely give flashable zip... Then give a try.... Rest your own wish.....
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I don't mind if I have to fastboot it vs. TWRP as a .zip, but I've been flashing out the yin-yang and I still have a few ROMs I want to try LOL. I'll get to this eventually....see how the feedback is first....plus I "need" root, not want...."need"...................LOL
mikeprius said:
I don't mind if I have to fastboot it vs. TWRP as a .zip, but I've been flashing out the yin-yang and I still have a few ROMs I want to try LOL. I'll get to this eventually....see how the feedback is first....plus I "need" root, not want...."need"...................LOL
Click to expand...
Click to collapse
mind that it will encrypt your device
The build.prop wifi tether method doesn't seem to work with the N preview at least in the traditional way. Has anyone managed to get it to work?

Categories

Resources