yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] rapha1403:
I've downloaded Ampere and did some short Tests.

My Battery was at 6% and it charged with 720mA with flightmode on and 650mA flightmode off. I trink the mA rate will get higher because it only charged with 3,5 v at the beginning.

I will do some Tests in my car too.

Next thing i noticed is that the tablet didnt go to Deep sleep at night.

Seems to be the Google now widget, I deactivated it and the Performance was much better.

But to be sure i used powermanager to put the tablet into deepsleep.
[Nexus 7 Android Development] CosmoLogic:
Congrats, great work! :D
[Nexus 7 Android Development] rapha1403:
Had time for a Quick test in my car.

Fastcharge in host mode seems to work fine.

Ampere showed a result of 850mA with bluetooth, GPS and 3g enabled.

My Music app was playing from the usb stick and Navigation app was activated.

In 2 weeks i will drive for about 4 hours and post my results.
[Nexus 7 Android Development] nalott:
I gave oxydo-revamped a try. I'm running Autodroid 1.2 (4.4.4 KK) with built-in Kangaroo kernel and am quite happy with that - except for the lack of real fast charge in any mode. I only got 850 mA whatever I tried, which lead to battery discharge under heavier load in car.

oxydo-revamped gives me just over 1 ampere under the same conditions. Both OTG or not, direct wall charge, measured with a proper (hardware) ampere meter. So it's better but still leaves something to be desired ;)

Anyway, thanks sgt. meow for your work! :good:
[Nexus 7 Android Development] rapha1403:
After some few New Tests i flashed timurs usb Rom.

I dont know if it's blissrom or the kernel but it didnt charge well.

With the original ac adapter Ampere showed about 800mA max over otg it dropped download to about 300-400mA.

I even did a fresh Flash, different cables unfortunately nothing helped.

But i will stick to this thread, keep up the work i would love to see my nexus running android 5.1.

For timurs Rom i dont have exact charging values, because Ampere doesn't work for android 4.1 but it doesn't discharge over otg (doesn't charge either :D)
[Nexus 7 Android Development] sgt. meow:
Thanks for the feedback. I'll keep it all in mind. The charging thing intrigues me greatly.

My busy schedule doesn't allow me to spend much time on this but I'll try my best to push out updates as frequently as possible.
[Nexus 7 Android Development] aarongdl:
Would anyone mind helping me to get this working? I'm installing this in my car and would like otg capabilities as well as charging.

I flashed my n7 (2012 wifi) to stock, rooted, flashed autodroid 1.2 (for 4.4.4) and then the "oxydo-revamp#3-4.9.zip" file as well via recovery, and I can't seem to get it to boot. I've tried a few different ways and don't seem to have ANY luck.

I've never been big on installing kernels, so I fel as if my error is there. I downloaded the kernel from post 104, it should only be 4mb, correct? (was wondering because the kangaroo kernel is around 43mb)
[Nexus 7 Android Development] rapha1403:
The kernel in autodroid is build for otg+charging.

You dont need to Flash the oxydo kernel.
[Nexus 7 Android Development] crzycrkr:
I haven't used this in a while, so someone can correct me if I'm wrong, but revamped is a lollipop kernel. You need to use the original oxydo kernel for autodroid. Also, check the autodroid threads. Getting it to boot the first time is a pain. Never booted for me with the installed kernel
[Nexus 7 Android Development] nalott:
I have no problem running revamped with Autodroid 1.2 (I only recommend this combination! It got me more stability.). I even had no problem with first boot just after having flashed Autodroid with it's (Kangaroo) kernel (no f2fs). Sorry for not particularly helpful post, I have no idea about the bootloops. Just wanted to show these statements are not generally true.

---------- Post added at 08:48 PM ---------- Previous post was at 08:27 PM ----------

Sorry if this was discussed, I could not find any related post in this thread.

Is a "timeout" (or any other) workaround of baseband_xmm_power issue applicable for the revamped kernel? I have no bb_timeout in /sys/module/baseband_xmm_power/parameters. The wakelock bothers me extremely.
[Nexus 7 Android Development] crzycrkr:
I guess I was wrong on the lollipop thing. As I said, it's been a while. But I will disagree on the booting issue. The autodroid threads are filled with people having problems with the first boot. Apparently there was a problem with the built in kernel. Flashing kangaroo or oxydo seemed to fix the problem
[Nexus 7 Android Development] sgt. meow:
Haha flashing this kernel actually fixes something then. That's great. Well not really because I dunno why that happens.

I'll try to add in the bb_timeout mod in the next build. As soon as I can find the time to actually get to it.
[Nexus 7 Android Development] sgt. meow:
Oh and Kangaroo is that large probably because of the several modules it ships in the ZIP file. Mine is mostly barebones zImage in an AnyKernel ZIP (that needs cleaning up as I just noticed).
[Nexus 7 Android Development] nalott:
Recently I've got some random reboots. For example today the tablet spontaneously rebooted on the shelf after some 16 hours in standby (I even haven't touched it at all). I tried to debug but apparently logging is disabled in oxydo-revamped? I'm getting this error:

Unable to open log device '/dev/log/main': No such file or directory

Nothing helped to enable log. I used to use logcat earlier with the same rom and different kernel. I even don't seem have /system/lib/modules/logger.ko.

Don't get me wrong - I'm not blaming oxydo, it may obviously be some app, I just need to find what's happening.
[Nexus 7 Android Development] konradit:
Is this kernel compatible with 5.1.1???
[Nexus 7 Android Development] fr4nk1yn:
Yes, I have it on LMY47V.
[Nexus 7 Android Development] konradit:
Can you share a dl link please? The one in the OP is down
[Nexus 7 Android Development] fr4nk1yn:
Uh, it's mentioned at the top of the OP, post 104.
[Nexus 7 Android Development] tesna:
Quick question, does this kernel also works with CM12.1? or only compatible with stock based roms?
[Nexus 7 Android Development] bill3508:
Running great on Orion LP. 1624 MHz nice. Thanks for the work.
[Nexus 7 Android Development] poissonn:
Curious to replace my autodroid setup with this one! However one big feature i like on autodroid is the possibilty to customize the nav bar buttons like this:

Is it possible with this kernel or any lollipop roms offering this possibilty? I'd switch right away!
[Nexus 7 Android Development] NeoPreacher:
this here is a kernel (thread) :confused: ... and got nothing to do with ui customizations. such questions belong to Q&A
[Nexus 7 Android Development] poissonn:
i know this is a kernel...I was simply asking if someone knew of a lollipop ROM available that was compatible with this kernel and that has similar features as the Autodroid ROM on kitkat!
[Nexus 7 Android Development] boom671:
any updates? I was having slow charging and and crashing after I flashed minimal rom. Any ideas?

Pat
[Nexus 7 Android Development] fr4nk1yn:
Appears to be a problem with an app. DAC audio is definitely working.
[Nexus 7 Android Development] oldman_58:
Loaded the Revamp 3-4.9 So far battery life is incredible on Nexus 3G...

Great job..
[Nexus 7 Android Development] boom671:
Anyone able to mount external HD? Tried multiple apps like stick mount to no avail.
[Nexus 7 Android Development] fr4nk1yn:
I don't believe OTG storage and charging is supported. I can't get it either.
[Nexus 7 Android Development] boom671:
aww....thanks. SGT.MEOW...could you add this? \

Pat
[Nexus 7 Android Development] sgt. meow:
I know, for a fact, that USB OTG + Charging works because I have tested it myself. I haven't tested it with external HDDs though.
[Nexus 7 Android Development] bass0324:
Auto mount of storage is not a feature of the kernel but a feature of the rom. I did get the developer of chroma for nexus 7 to implement this, and tested it working in the latest chroma build.
[Nexus 7 Android Development] fr4nk1yn:
Good news! I have to admit I thought auto mount was built into lollipop and never tried stick mount.
[Nexus 7 Android Development] Old Guy:
I am running this kenel on Lollipop and can confirm it will mount a usb hard drive and charge using stikmount.
[XDA Assist] muqrimusa:
I wiped my Internal Storage through TWRP because my laptop can't detect my One M8 and I thought wiping the internal storage would fix the problem. I have tried wiping Dalvik Cache, Data and Cache and none of it helps thus without reason I wiped the internal storage.

When I reboot, my lock screen doesn't show up so does my status bar (cant even slide down to show notification), and also my on screen buttons. I tried to re-flash the ROM, idk what else I should re-flash but it didn't solve the problem. And still my laptop cannot detect my One M8. Also there is no TWRP backup to restore my phone back to Sense 6 ROM. (maybe the wipe deleted the backup, idk, it was there before).

Someone help me, I don't think any mobile shops in my country can fix this problem. There is no one to help me here. I can't even sell the phone because no one would want to buy an already damaged phone. SO please I beg for your help. Anyone I would be grateful for your reply. Should you require any information to solve this problem I would do my best to provide you with it. Thanks in advance.
[XDA Assist] :
Hi,

Need to know which M8 carrier version you have to point you towards help.

Also, try reinstalling HTC sync on your PC to restore drivers. If your computer won't see your device, you are not going to have much luck.
[XDA Assist] mxqrimusa:
I will try that. How can I fix the lock screen, status bar and the onscreen navigation buttons not showing up? also google now launcher background is all black even when i change the wallpaper. A few days ago after I wiped the internal storage a "system.android has stopped" showed up which caused these problems. I did a reflash of the ROM and still the problem exists.
[XDA Assist] :
You need to tell me your carrier version, so I can point you towards help.

XDA Assist is here to help navigate the site, not for support. ?
[XDA Assist] mxqrimusa:
Mine is the international version. (I live in Brunei)
[XDA Assist] :
Then here is where to ask for help,

http://xdaforums.com/htc-one-m8/help/help-thread-htc-one-m8-questions-t2897783
[Android Software/Hacking General [Developers Only]] xpirt:
Introduction

You probably know already that starting from Android 5.x (Lollipop) compiled roms (aosp,cm,stock) are not compressed anymore the way they used to be on previous android versions. On previous versions all content inside /system folder that has to be extracted within our device was either uncompressed (simple /system folder inside our flashable zip) or compressed in a system.img file, which it is a ext4 compressed file; both of these, anyway, were readable and we could see all system files (app,framework, etc).

The problem comes in >=5.0 versions, this method is not used anymore. Why? Because roms started to be always larger, so it is necessary to compress them even more.

What does new Android zips (full roms, but also otas) contain?

New Android flashable zips are made this way:

boot.img (kernel)

file_contexts (selinux related)

META-INF (folder containing scripts)

system.new.dat (compressed /system partition)

system.patch.dat (for OTAs)

system.transfer.list (see explanation below)​

What does updater-script contains then?

The updater-script uses a brand new function: block_image_update(), this method basically decompresses necessary files inside the device. Let's study it.

From google git source code, if we go inside the new file /bootable/recovery/updater/blockimg.c, we find at the end of it the registration of the function block_image_update() as the method BlockImageUpdateFn() which starts at line 254. Here finally we find all information we need to know about the decompression of the .dat file(s). First file we analyze is system.transfer.list which Google tells us:

But what each line means?:

Ok, but how to decompress the system.new.dat file?

All instructions are below. sdat2img, rimg2sdat and img2sdat binaries are involved. Please read carefully step by step.

NOTE for OTAs

If you are looking on decompressing system.patch.dat file or .p files, therefore reproduce the patching system on your PC, check imgpatchtools out by [MENTION=6298645]erfanoabdi[/MENTION].

You can use/modify these files and/or include them in your work as long as

proper credits and a link to this thread

are given.

If you have questions or problems write here ;)

Are you building from source and want to revert to the old flashing method without DAT files?

Do this (thx [MENTION=5666997]Elluel[/MENTION]):

1 - Delete this line

2 - Make sure you have this commit

Thanks

- howellzhu & luxi78 - for initial source codes

- all contributors from github
[Android Software/Hacking General [Developers Only]] xpirt:
Ubuntu

Ubuntu 64-bit - Guide

Step 1 - Decompressing = DAT (sparse data) -> EXT4 (raw image)

We're now using sdat2img binary, the usage is very simple (make sure you have python 2.7+ installed):

./sdat2img.py <transfer_list> <system_new_file> [system_img]​

- <transfer_list> = input, system.transfer.list from rom zip

- <system_new_file> = input, system.new.dat from rom zip

- [system_img] = output ext4 raw image file

and a quick example:

./sdat2img.py system.transfer.list system.new.dat system.img​

by running this command you will get as output the file my_new_system.img which is the

raw ext4 image

.
​

Step 2 - Decompress EXT4 (raw image) -> OUTPUT folder -> Compress EXT4 (raw image)

Now we need to mount or ext4 raw image into an output folder so we can see apks/jars etc.

To do this we need to type this command:

sudo mount -t ext4 -o loop system.img output/​

As you can see there is a new folder called output which we can edit/modify/delete your files (not able to? see here)

Now we need to compress it back to a raw ext4 image, to do this we need the make_ext4fs binary. Make sure you have the file_contexts file (taken from the Rom zip) inside the make_ext4fs path. Then type this (got issues? see here)

./make_ext4fs -T 0 -S file_contexts -l 1073741824 -a system system_new.img output/​

You will get the new raw ext4 image called 'system_new.img' ready for the next step.
​

Step 3 - Converting = EXT4 (raw image) -> IMG (sparse image)

Now we need to convert the ext4 raw image into a sparse image. For this you need img2simg binary you can find here (thx to [MENTION=2976903]A.S._id[/MENTION]).

The usage is simple:

img2simg <raw_image_file> <sparse_image_file>​

Pretty self-explanatory, the output will be a new sparse image (.img).
​

Step 4 - Converting = IMG (sparse image) -> DAT (sparse data)

Now we need the img2sdat binary, the usage is very simple (make sure you have python 2.7+ installed):

./img2sdat.py <system_img>​

- <system_img> = name of input sparse image file (from step 3)

As you can see the output is composed by system.transfer.list, (system.patch.dat) & system.new.dat, ready to be replaced inside your Rom zip.
​

DOWNLOADs

sdat2img.py

- github.com

make_ext4fs

- mega.co.nz

img2sdat.py

- github.com
[Android Software/Hacking General [Developers Only]] xpirt:
Source - Changelog

sdat2img

Repo: https://github.com/xpirt/sdat2img

Changelog: https://github.com/xpirt/sdat2img/commits/master

Source: https://github.com/xpirt/sdat2img/blob/master/sdat2img.py

img2sdat

Repo: https://github.com/xpirt/img2sdat

Changelog: https://github.com/xpirt/img2sdat/commits/master

Source: https://github.com/xpirt/img2sdat/blob/master/img2sdat.py
[Android Software/Hacking General [Developers Only]] xpirt:
Windows

Windows 32/64 bit - Guide

Step 1 - Decompressing = DAT (sparse data) -> EXT4 (raw image)

We're now using sdat2img.py binary, the usage is very simple (make sure you have python 3.x installed):

sdat2img.py <transfer_list> <system_new_file> <system_ext4>​

- <transfer_list> = input, system.transfer.list from rom zip

- <system_new_file> = input, system.new.dat from rom zip

- <system_ext4> = output ext4 raw image file

and a quick example:

sdat2img.py system.transfer.list system.new.dat system.img​

by running this command you will get as output the file my_new_system.img which is the

raw ext4 image

.
​

Step 2 - Decompress EXT4 (raw image) -> OUTPUT folder -> Compress EXT4 (raw image)

Now you should either move to Ubuntu x64/x86 or follow the 2nd step from the Ubuntu guide on cygwin 32 bit.
​

Step 3 - Converting = EXT4 (raw image) -> IMG (sparse image)

Now we need to convert the ext4 raw image into a sparse image. For this you need img2simg binary you can find here (thx to [MENTION=2976903]A.S._id[/MENTION]).

The usage is simple:

img2simg.exe <raw_image_file> <sparse_image_file>​

Pretty self-explanatory, the output will be a new sparse image (.img).
​

Step 4 - Converting = IMG (sparse image) -> DAT (sparse data)

Now we need the img2sdat binary, the usage is very simple (make sure you have python 2.7+ installed):

img2sdat.py <system_img>​

- <system_img> = name of input sparse image file (from step 3)

As you can see the output is composed by system.transfer.list, (system.patch.dat) & system.new.dat, ready to be replaced inside your Rom zip.
​

DOWNLOADs

sdat2img.py

- github.com

make_ext4fs

- mega.co.nz

img2sdat.py

- github.com
[Android Software/Hacking General [Developers Only]] Corvo007:
Is there any tool to browse (and/or manipulate) these .dat files in Windows?
[Android Software/Hacking General [Developers Only]] xpirt:
i don't think so, though you can install ubuntu in a virtual machine as 64-bit and decompress there without problems.

edit: windows binaries added to OP.
[Android Software/Hacking General [Developers Only]] Corvo007:
I found one, Ext2Explore, it can browse and extract lollipop .dat files
[Android Software/Hacking General [Developers Only]] chihliouma:
Can you explain how to work in more detail ? Thanks.
[Android Software/Hacking General [Developers Only]] Corvo007:
With that application you can open the system.new.dat file like a zip archive

Sent from my Nexus 5
[Android Software/Hacking General [Developers Only]] Incredible_Culp:
Confirmed.

Works perfectly..

Thanks a lot! This will save a lot of time theming.. (pulling the system, settings, framework without having to flash the rom first)

Oh, just for s&g's i extracted ("decompiled") the system.new file, the files (app, prive-app, framework, media, etc) all got placed on my desktop -- i deleted the system.new file from the rom -- i then placed the folders and files that got extracted and placed them in the rom -- i flashed it -- it booted! lol.. didnt think it would... but anyways, there's that.

For those who want to try:

--- > its basically self explanatory.

- once downloaded (the link above) extract the contents from the zip (i just went ahead and extracted to my desktop)

- right click the linux penguin

- run as administrator - the window will pop up

- go to file > open image > find your system.new image (should already be extracted from the rom and placed on your desktop)

- click open

- you should now see your image (or path) in the windows -- double click them (i doubled clicked both the right and left side)

- now you should be able to see all the folders

---> if you want to extract those folders

- just go up to the top

- click save and choose an extraction :) (i chose Desktop)

Hoped i helped -- any questions or confusion, dont be shy to ask -- i probably went too fast, idk lol

Enjoy!
[Android Software/Hacking General [Developers Only]] webdroidmt:
I can't get this to work at all. I'm using Win 7 Pro and I've actually used this app before with stock Nexus 7 factory images and it worked fine.. What file did you actually download? I d/l 2 different versions, one was beta 2.0 and the other was a zip that said 2.2.71 but the about on the exe says 2.1, which is the version I've been using for quite a while.

With the beta 2.0, there's not even an option to open a file and with the 2.1, it errors out every time. After opening system.new.dat image and double clicking, it just hangs and the program stops responding. If I try clicking on it and selecting save, it allows me to select a folder to save it in but I just get a dialog box that says saving files and then hangs at 24% every time, finally crashing with a Microsoft C++ runtime error.

Oh btw, you didn't go too fast LOL, this is really a simple app to use but it's just not working for me with these block image files. Maybe I'm missing something but it's got me scratching my head. :laugh: If you have any ideas, I'm all ears.

Thanks,

Mike T
[Android Software/Hacking General [Developers Only]] Incredible_Culp:
hmm interesting..

im using windows 8.1

idk how much help i can be because i just downloded the first option (provided by the link above) and went from there.

like you said, theres two.. the .exe and the .zip.. i downloaded the .exe
[Android Software/Hacking General [Developers Only]] webdroidmt:
So, did you d/l the zip that was modified 2006-8-26, which is version 2.0 beta, or did you click the link which said download latest release?

Mike T
[Android Software/Hacking General [Developers Only]] Incredible_Culp:
ha! didnt even see there was a latest release..

i downloaded the 2006-8-26 apparently -- didnt even look at that date either LOL

i dont want to try the latest now -- this one works fine for me lmao -- dont want to ruin it.. ah, screw it, im downloading the latest now

EDIT: Ok, i lied.. i just checked my trash.. i did download the lastest release .zip .. the 2271..
[Android Software/Hacking General [Developers Only]] Elluel:
[MENTION=4393788]webdroidmt[/MENTION] [MENTION=2572565]Incredible_Culp[/MENTION] Download from here lol: http://sourceforge.net/projects/ext2read/
[Android Software/Hacking General [Developers Only]] webdroidmt:
Maybe something with my PC setup or Win 7 because the 2006-8-26 version doesn't even give me an option for opening a file image. It actually loads up looking like an incomplete application, it's also a very small filesize. Did you just d/l the ext2explore exe, or did you also d/l ext2read2 beta zip?

Mike T
[Android Software/Hacking General [Developers Only]] Elluel:
Use the download link in the above post and click the green download button, and it should be the correct version, from 2012 rather than 2006.
[Android Software/Hacking General [Developers Only]] webdroidmt:
That's the one I've been using for quite some time. As mentioned in my previous post, the system.new.dat file just "appears" to be saving but hangs at 24%, then eventually crashes. I'm stumped, should be so easy but it doesn't want to cooperate. LOL

Thanks anyway,

Mike T
[Android Software/Hacking General [Developers Only]] Elluel:
Weird. Try redownloading the ROM you're trying to extract?
[Android Software/Hacking General [Developers Only]] webdroidmt:
Thanks for trying guys, that is exactly the one I've been using. I downloaded it again a few seconds ago and still getting the same result. :confused: :laugh:

Thanks.

Mike T

---------- Post added at 01:09 AM ---------- Previous post was at 01:08 AM ----------

I've actually tried with images from 3 different roms and they all give me the same result. It's cool, I just won't be able to play around as much as I used to porting stuff.

Mike T

---------- Post added at 01:15 AM ---------- Previous post was at 01:09 AM ----------

Just curious, you guys aren't changing the file extension to something other than .dat, right?

Mike T
[Android Software/Hacking General [Developers Only]] rayman95:
got problem with this....extract the rom with system extractor and modify updater script with this...try the both without success.....

the flash is very fast , got following message

"mount : failed to mount/dev/block/platform/msm_sdcc.1/by-name/system at/sustem: Device or ressorce busy"

and i'm stuck on boot screen with kernel not seandroid.....

maybe if I share my "rom" someone can say me what's wrong????