yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] julietnour:
No, I 'll try that but my MacBook Pro OS X 10.8.5 is saying that my HTC Desire 530 'smartphone' is offline. Does it matter if my MacBook Pro OS X 10.8.5 saying that my HTC Desire 530 'smartphone ' is offline when I'm using the command ./adb devices in terminal?
[Android Q&A, Help & Troubleshooting] HelpMeruth:
reboot you device to bootloader and type "fastboot devices" if your device is listed than you're good. you dont have to be booted in android
[Android Q&A, Help & Troubleshooting] julietnour:
Thank you and I'll tried that.

?
[Android Q&A, Help & Troubleshooting] julietnour:
I've tried that and I'd no luck.
[Nook HD, HD+ Android Development] Lanchon:
you can now use REPIT to increase the size of the /system partition on the Nook HD/HD+ to 1 GiB to support the newest roms with gapps. while you do this, you can optionally also add 0.5 GiB of free space to /data. the extra space is repurposed from partitions that go unused in custom roms.

see the details here:

https://github.com/Lanchon/REPIT/issues/59

full doc for REPIT is here, please read it:

https://github.com/Lanchon/REPIT

additionally, this note can be interesting for users and rom developers alike:

https://github.com/Lanchon/REPIT/issues/56

this is for Nook HD+ only, but HD owners can request a port of REPIT by following the instruction in the doc page.

UPDATE: a port request was submitted by BultoPaco and now REPIT supports the Nook HD too.

thanks!
[Nook HD, HD+ Android Development] ajislav:
This is great. Would also be helpful if you included information on how to go to stock partition layout, but big thanks indeed.
[Nook HD, HD+ Android Development] Lanchon:
added to the github note.
[Nook HD, HD+ Android Development] king200:
Following the guide \https://github.com/Lanchon/REPIT/issues/59 to increase /data,

"you can also add approximately 0.5 GiB to /data"

Does it make difference if the Ovation is 16gb or 32gb model
[Nook HD, HD+ Android Development] Lanchon:
this was made and tested with the 16GB version. in all other devices REPIT has been smart enough to adapt to these differences automatically. it should work with the 32GB version. but if there's anything strange or too different, REPIT will bail instead of messing up your device.
[Nook HD, HD+ Android Development] prsa01:
Ext4 only?

Mine returns an error not able to read superblock on data even if I am only trying to expand system. my data and cache are f2fs. Is that the problem? I'll cut/paste the log here when I'm back on my ovation.

This with the 3.0.2 twrp currently in experimental folder

Update: OK, went back and reread the general instructions. Looks like doesn't work for f2fs. I did convert cache to ext4 and set data=same, but still returned error.
[Nook HD, HD+ Android Development] acr123:
Using Android 7 and latest TWRP on Nook HD+. Downloaded repit file zip, renamed as per instructions & downloaded delete stock rom zip. Flashed delete stock rom in twrp w/o problems. Flashed renamed repit file and Got error 1 after flashing. Told to reboot and flash from tmp folder and also got error 1. The error related to unable to reload partition table and unable to mount all partitions. Info from file manager shows using 5.11 GB out of 27.01 GB of internal storage

Any ideas???.
[Nook HD, HD+ Android Development] tsoheq:
I just did this today.

I tried to flash lanchon-repit-XXXXXXXX-factory=same-system=1G-cache=112M+wipe-data=same-ovation.zip using twrp, but it gave me errors. I tried to follow the instructions to flash the file from the /tmp folder that it has copied, but it still gave me errors about /emmc partition not able to be umounted. I tried this a few times according to instructions posted on github but still no-go.

This is how I got around the issue:

I went into TWRP's Advanced menu and open up Terminal. Then I did

umount -a

There will be some errors that some partition cannot be umounted (eg. /tmp). I ignored that.

Now, I flashed the REPIT script again from /tmp folder. This will now run the script, but at the end, it will fail with the error about not being able to write /etc/fstab file. I ignored that (Android's file is /fstab.ovation).

Then I went ahead and flashed a cm13 build as usual. After rebooting into cm13, I opened up terminal and then did a df. I could see that /system partition had then expanded to 1034136 1-K blocks, which was roughly 1GB. Hoping that the partition will stay, I then flashed a gapps package, and it went through. On rebooting, I found that about 73% of the /system partition was used (it was around 55% without gapps). So, everything seems to look good.

Hope that helps.
[Nook HD, HD+ Android Development] gascomm:
I tried following this unsuccessfully - any chance of an idiot's walkthrough?

I got as far as running the report file from tmp with no errors but when trying to flash Pico gapps I'm told it runs out of space. so close and yet I'm too thick to know what I'm doing wrong :(
[Nook HD, HD+ Android Development] tsoheq:
What was the partition size when you do a "df" in a terminal? If it did expand, then the df command should show you the expanded /system partition size.
[Nook HD, HD+ Android Development] Lanchon:
f2fs partitions cannot be resized without wiping on planet earth. if there exists an f2fs resize tool, only aliens have it.

you can can wipe data (not recommended) or you can flash the standard repit to simply grow /system with /cache if you want. /data will not be enlarged of course.

f2fs on /cache is stupid, don't ever do it!!! only /data should be f2fs.
[Nook HD, HD+ Android Development] Lanchon:
this has been explained to death now, read the REPIT docs for the solution. create a github issue WITH THE REQUIRED INFO (as detailed in the docs) if you need official support.
[Nook HD, HD+ Android Development] Lanchon:
you didn't need to reflash system of course, REPIT keeps the data as explained in the docs. glad it worked.

btw, it is enough to follow the docs about unmounting partitions using the TWRP UI.
[Nook HD, HD+ Android Development] Lanchon:
read the docs, everything is there. you can't be helped if you don't provide the REPIT log. (that is also stated in the docs, btw.)
[Nook HD, HD+ Android Development] asksmity:
Can confirm this works on 32gb ovation. Just finished after a bit of fighting. As always, YMMV but this was the process I followed:

Ran the delete file. Success.

Ran the resize file, errors.

Ran the resize file from tmp, errors.

Ran "umount -a" from terminal then reran resize from tmp, errors.

I found both my data and cache partitions were f2fs. Formatted both back to ext4 since f2fs cannot be resized. This was easy for me as I had all the important stuff backed up but be sure to back your data up before doing this, it will wipe the partition.

After the wipe I loaded one file on to the data drive, the renamed resize file.

Tried running the resize file. Unmount errors and the run from tmp message.

Went into terminal, ran "umount -a" 3 times. The first I got several errors, the second and third only one.

Went into tmp and ran the file. After realizing the process was working and was going to take a while, I plugged up the charger (wall, not pc) and let it set overnight.

Came back this morning to one error, the fstab error. No unmount errors though.

Remounted the drives in twrp and ran "df" in terminal. 1gb system.

Rebooted and ran through the setup

Reloaded my roms/gapps folder manually via USB

Rebooted to TWRP and ran opengapps pico. Completed succesfully.

Rebooted and had play store in apps. Logged into gapps.

Thank you Lanchon, this helps bring life back to an old love.
[Nook HD, HD+ Android Development] Lanchon:
you are welcome!

lol! why not read the docs??? :)

if you wanted to change the file system in /data to ext4 all you needed was to change:

-cache=32M+wipe-data=max

to:

-cache=32M+wipe-data=max+wipe

which is the same as:

-cache=32M+wipe+ext4-data=max+wipe+ext4

given that ext4 is the default fs for /data and /cache.

using -data=max+wipe would have been so much faster than moving a huge empty partition around!!! it would have finished the operation in around a minute. not to mention adding less wear and tear to the emmc of your aging device.

the file system in /cache was never a problem, you did not need to change it back to ext4. you were using -cache=32M+wipe which means that REPIT would resize/move the partition without keeping its contents (wiping) and without regard for the previous file system type and state (ie, whether it had errors, etc).

if you wanted to enlarge /data AND ALSO KEEP /DATA AS F2FS, all you needed was to change:

-cache=32M+wipe-data=max

to:

-cache=32M+wipe-data=max+wipe+f2fs

f2fs cannot be resized, but it can be moved/resized while wiping. (ie, the partition can be recreated from scratch with the new size, if data retention is not required.) this is all explained in the docs, seriously lol...

https://github.com/Lanchon/REPIT#partition-types

using an f2fs /cache partition is dumb and completely useless. all who have f2fs /cache are adviced to change /cache back to ext4 and leave it that way.

regarding the umount stuff, maybe your TWRP has an issue, but i'm willing to bet that if you followed instructions to the letter, you wouldn't have needed all that. the guy that requested the ovation port of repit (look for the github issue (closed now)) and first ran the test version did not have any of this issues. the TWRP he used is documented in the port request.

anyway, thank you very much for documenting what worked for you!
[Nook HD, HD+ Android Development] asksmity:
Very good info above!

I could have done that as well, and probably should have. But there was conformation in the thread that the options I renamed to worked. So for me being a "part timer" I wanted to make sure that I was not the reason for the issue (ie: fat fingering an extra letter in one of the options or misplacing an option). I have a bad habit of screwing things up.

As a recommendation, it might be a good idea to include some of these sample options in you main thread and explain what they do. I know I know, docs docs docs but it helps us roughians and would probably keep the issue posts down.

Thanks again for the tool and the feedback!
[Nook HD, HD+ Android Development] BultoPaco:
I read all the docs and used Lanchon's tip above to wipe /data and retain f2fs file structure. Got an error running it from my SD card but, when I ran it from the internal tmp folder (as instructed), it worked perfectly. Thank you [MENTION=4141005]Lanchon[/MENTION]! I'm going to request a Hummingbird version so I can have both of my Nooks optimized?
[Nook HD, HD+ Android Development] Jazviper:
Is this supposed to provide more space for Gapps? I ran this and it worked with no errors, but I can't install any different sized gapps than nano.

EDIT: nano is still too big too.
[Nook HD, HD+ Android Development] Lanchon:
read:

https://github.com/Lanchon/REPIT/issues/56

tl;dr: you can fix this by pressing the resize partition button on twrp.
[LG Leon Questions & Answers] 11themikster11:
Downloaded media drug app install it when i touched on it it said it was scanning it but then said it was unable to scan so i cant use it is there a way to correct this
[Galaxy Grand Prime Q&A, Help & Troubleshooting] PenguinRed:
I recently rooted the phone and now randomly reboots by itself sometimes. One reboot fuvked up the rom and now its stuck on rebooting by itself every 6 seconds. i cant get to odin mode or recovery mode. any help?
[Galaxy Grand Prime Q&A, Help & Troubleshooting] Eduardo 6u9:
It is a deadlock. Install WakeLocke in Google Play and activate "PARTIAL_WAKE_LOCKE", reboot your Grand Prime and bye bye deadlock! :)
[One (M7) Q&A, Help & Troubleshooting] Afzal922:
After Installing Elemental X on my Htc m7 wls, No sim card is detected, No Network, Unknown IMEI and Badeband version, Radio version is not shown in Bootloader, Moreover Device is auto rebooting after two minutes, plz help.
[One (M7) Q&A, Help & Troubleshooting] Tepmued:
Help me plese.
[One (M7) Q&A, Help & Troubleshooting] lucyr03:
Try to flash ruu.
[Huawei Ascend P7] Roldan1983:
Hi all!

Well I have a P7 L07 Factory model, and I wanna change to L10.

The first problem is I've wasn't able to find:

1. how back to stock recovery..

2. how change to L10 factory model

and 3. not fallen link...

I wanna get Miui 7 but I need L10 in order to don't have sim card problem

Anyone could help me?

Thx 4 advance!
[Huawei Ascend P7] najor1988:
Roldan amigo yo te puedo ayudar con eso... Escribeme por privado y te doy un metodo que cree yo para teber todos los recoverys

Enviado desde mi HUAWEI P7-L07 mediante Tapatalk
[G4 Original Android Development] ashkan-khatar:
Pyrophag is a customized system image for the 818P based off of completely stock v20h factory image.

There is absolutely no change in appearance, except for LG's stock font Foxrain, which has been replaced with Roboto Condensed (a favorite font of mine); so the ROM is suitable for those who are interested in stuff "under the hood" only. It's basically a boosted stock ROM.

​

Buttery smooth, incredibly optimized and stable performance all over the ROM;

Significantly reduced amount of heat produced during heavy tasks;

Dual Window for all apps;

60fps FHD video recording;

Slow Motion video recording;

100% photo quality;

Completely stock looks;

​

None

​

***YOU WILL NEED TO HAVE MARSHMALLOW (preferably v20h) INSTALLED IN ADVANCE***

***THE PROCEDURE IS SAFE AND NO ISSUE SHOULD HAPPEN. NEVERTHELESS, I DO NOT ACCEPT RESPONSIBILITY FOR POTENTIAL BOOTLOOPS/DATA LOSSES OR ANYTHING DURING OR AFTER THE PROCESS***

Backup everything to SD Card through LG Backup;

Extracted the downloaded file (the ROM) and copy s.img into the internal memory of your device;

Turn off the phone, wait for the blinking notification light to go off, press and hold volume up button and connect the phone to your PC simulataneously (do make sure in advance that you have all required drivers installed) to enter Download Mode;

Now open LGUP, choose a v20h KDZ and press Start Flashing;

Keep an eye on the percentage and the other on the phone. As soon as the percentage reaches 9, look at the phone, and the moment a green port number (e.g. COM6) appears on the screen, disconnect the phone immediately (or everything will be erased on your internal memory, so you'll have to copy the system image again) and close LGUP;

Open the folder you have assumingly extracted LG_Root files in, hold down the shift button, right click on the window and choose Open Command Window Here;

Type "Send_Command.exe \\.\COMX" without the quotation marks (X represents the port number shown on your phone);

If you have all drivers installed, you'll be able to commmunicate with the driver now. Type "id" and you should get a response. If so, then it means everything is all right and you're good to go;

Carefully input the following command and press Enter. It will go to a new line and an underscore will start blinking. After a couple of minutes, a hashtag sign will appear. Type "LEAVE", plug out the device, pull the battery and re-start the phone.

dd if=/data/media/0/s.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0

Enjoy!

​

Attached

​

DPI 640 (normal)

DPI 540

​

[MENTION=7514965]jskasia[/MENTION], [MENTION=7372544]warBeard_actual[/MENTION], [MENTION=1867148]Pfeffernuss[/MENTION]

Status: Stable

Android Version: 6.0

Linux Kernel Version: 3.10.84
[G4 Original Android Development] jskasia:
Great work, many thanks. :good:
[G4 Original Android Development] MitoTakatori:
Another development thread for H818p! Thanks mate! Gonna try this one! It's great if the ROM will have a 540 dpi variant. :good:
[G4 Original Android Development] jskasia:
You can do it yourself see this => http://android.wonderhowto.com/how-...creen-resolution-without-root-access-0160439/
[G4 Original Android Development] MitoTakatori:
Thanks! Got to try this. Won't this affect anything in the rom?
[G4 Original Android Development] jskasia:
I guess not.
[G4 Original Android Development] MitoTakatori:
Nice. Thanks. Does Genisys theme still have issues with V20H?
[G4 Original Android Development] jskasia:
Yes, it is.
[G4 Original Android Development] ashkan-khatar:
It will. Icons will be messed up. The menu icon will be enlarged by, say, 20, and lockscreen shortcuts will disappear. If you really want a 540 dpi version, I could make one.
[G4 Original Android Development] ashkan-khatar:
I apologize to those who had wanted to download the ROM but failed. I hadn't made the link public. It's fine now.
[G4 Original Android Development] MitoTakatori:
I see. Hope it'll be solved soon. Thanks mate.

---------- Post added at 18:15 ---------- Previous post was at 18:13 ----------

Hi. I see. If it's okay, I do want a 540 or if 530 dpi is possible, then I do want that one. Thanks in advance mate! :good:
[G4 Original Android Development] marjunsyakir:
I want... Hehehe...

Thanks before for make lg g4 alive
[G4 Original Android Development] sandrox96:
Screenshots can be?
[G4 Original Android Development] BananowyPotwor:
Can u make H815 version?
[G4 Original Android Development] MitoTakatori:
I'll wait for the 540 or 530 dpi variant mate.
[G4 Original Android Development] phuonglev:
You can use osfmount to modify build.pro or use minimal ADB for any dpi you want, it's very simple and can find by google
[G4 Original Android Development] JoRoGe:
Yes, please, H815 version.
[G4 Original Android Development] marjunsyakir:
Any problem with playstore bro if i do this?
[G4 Original Android Development] ashkan-khatar:
Changing DPI through adb has consequences, you shouldn't do that. It'll mess up with icons.
[G4 Original Android Development] ashkan-khatar:
Update:

DPI 540 version added

-

Screenshots added

(though, no visual difference, really, comparing to stock; I've only tried to show the slight differences like Dual Window)- [MENTION=7112054]sandrox96[/MENTION] [MENTION=5357852]MitoTakatori[/MENTION]
[Galaxy S 4 Themes and Apps] Dang !!!:
Hi all,

I want to know we s4 i9500 users can change the animation while our device is switched off and charging..

I'm now on pacman ROM kk, as I tried with carbon, paranoid, even miui kk build, but no anim.. Only dark screen.. I know it is charging.. But it is a bug or what.. Anyway i like change it.. I googled.. But finding only about xperia devices.. only with gtbluesky miui kk build shows off.charging anim..

Anybody having any ideas or guide to solve my issue..
[Galaxy S 4 Themes and Apps] Dang !!!:
These are screenshot I taken of my current rom
[Moto Z Accessories] Turbojugend:
Picked up a high-speed MicroSD card and formatted it in my moto z. My device gets hot and full charge battery only lasts about three hours. When I remove the MicroSD card everything goes back to normal.

Using custom kernel and prerooted stock rom.

Anybody having any issues like mine or can shed some light on how to fix the issue? Thanks!
[Moto Z Accessories] reiteravi:
happened to me in moto x force and moto z

with 128gb lexar (works flawlessly on samsung tab a)

changed to sandisk uhs-i and no problems

might be moto is picky when it comes to sd cards
[Moto Z Accessories] Turbojugend:
Yep this is a lexar card. Was on sale for $100. I guess I'll have to return it. Thanks for letting me know.
[Moto Z Accessories] Turbojugend:
I went back to stock encrypted and it seemed to fix the issue.
[Moto Z Accessories] reiteravi:
don't count on it
[Moto Z Accessories] enetec:
Just FYI...

I've a 128 GB 1000x Lexar on my Moto Z with stock kernel and no issues with it... :fingers-crossed:
[Moto Z Accessories] Turbojugend:
So another update, turns out Android sucks at indexing and it was constantly scanning my 5800 FLAC files all the time. 100% battery would go to 10% in just under three hours, it had nothing to do with it being a lexar card!

Solution? I put a .nomedia file in my music folder and enabled my music player to ignore that and it scans my whole library with ease. I went to work at 8:30 am today and just got home (6:18 pm) and my battery is still at 85%.
[Moto Z Accessories] enetec:
Really a weird issue... :eek:

I've my MP3 and videos on my SD card and I've noted no issue with them... :confused:
[Moto Z Accessories] Shadowdancer123:
I've tried multiple high speed UHS-I cards, and formatted as internal, but all of them were either flagged by the phone as "too slow and might affect performance" or gave me heat and battery life issues.

And it would take five minutes after a reboot to show all app icons, or apps would lose login passwords, games lost saves and other annoying issues.

Formatting it as external storage, and just setting the camera to record directly to it works fine though.

Someone from Xiaomi actually said they're not adding or supporting MicroSD as internal due to them always having issues apparently. And it seems to be true.
[Moto Z Accessories] enetec:
This is in fact my actual situation... no issues with Lexar 128GB 1000x. ;)
[Moto Z Accessories] Turbojugend:
Maybe because I am using FLAC and have 5900 of them on it hahaha.
[Moto Z Accessories] enetec:
Probably! :laugh:
[Moto Z Accessories] Shadowdancer123:
Btw, another reason to not use it formatted as internal storage, is the immense power requirements MicroSD can spend at max write speed.

According to Wikipedia, as much as 100mA, which really explains why the phone heats up when it's formatted that way. And that doesn't include the consumption of the sd card controller.

https://en.m.wikipedia.org/wiki/Secure_Digital
[Moto Z Accessories] Turbojugend:
It didn't matter how I had it formatted before it was still getting super hot. Now that I haven't been using it, the issue must have been Android trying to index all the files as it's been running fine all week now that I have that .nomedia file in my music folder.
[Moto Z Accessories] masterjay21:
Does anyone know of a 128 card that can handle is phone?? Im gonn try the Samsung Pro+ 128
[Moto Z Accessories] enetec:
Using Lexar 1000x with no issues at all here...
[Moto Z Accessories] enetec:
And at last... I had issues too! :rolleyes:

On sdcard I store TWRP backups (no issues...), Titanium backups (no issues...), Maps (no issues...) and.... Pics & videos... and here I begin to see some weird behaviour... :eek:

First I saw Gallery had difficulties on showing pics thumbnials if I go fast between them... then it begins to show some "damaged" pics... at last I saw Camera app begins to crash just after taking a pic... (set to save on sdcard...) :rolleyes:

So, I removed sdcard, connected to a PC and copied all files... The copy requested A LOT of time since of read difficulties, BUT all files was ok at last. :highfive:

Then I formatted sdcard and extensively tested with h2testw with no issues and constant speed.

So I formatted again and copied all files back in.

Then I've found a way to have it working fine with Moto Z... (I think... :fingers-crossed:)

Problem is that Moto Z is set to use a too small cache size for modern sdcards (128 KB) and this probably generate sync issues (and when this happens I saw CPU go wild and phone become warm... in a very similar way with Windows when it is having issues with USB keys... :rolleyes:)

So I installed "SD-booster" app from Play Store (yes, it requires root...) and used it to resize cache to a more suitable value of 2048 KB and I haven't had any issue since then... more, my gallery has never been so fast scrolling and taking a LOT of pics in seconds or slow motion video isn't an issue at all now... ;)
[Moto Z Accessories] chucky91:
I'm using a Samsung Evo 128go and I have no issue
[Moto Z Accessories] Mouahmong:
So, I currently only use my 128gb Samsung UHS1 card for external storage only because of the issues other have experienced using it as internal. Not sure if it's on anyone's radar but Sandisk just announced a new micro sd card made specifically to be able to handle the read/write requirements.

http://www.droid-life.com/2017/01/05/sandisks-new-256gb-a1-microsd-card-wants-apps/