yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] l3v5y:
Sorry, I should have been more clear.

Basically, in most of my ROMs I install apps from the storage card as creating an OEM package doesn't always work.

The in built AutoRun.exe can't/won't process cabs on the storage card (no it's not just my config or the cabs).

To install apps from the storage card, UC is the most effective method and allows me as a ROM cook to provide a more complete ROM without wasting space for both the cab and the installed files on the device.
[Windows Mobile Development and Hacking General] Sleuth255:
I'm assuming you choose the storage card to save the wasted space the cabs would take up when customizing in this manner. Hmmm...

AutoRun will process cabs on an SD card (SDAutoRun actually runs AutoRun to do this) but they would be removed from the card unless they were RO. AutoRun can't directly read a config file that's located on the SD card however. That's why SDAutoRun copies SDConfig.txt to \windows.

At any rate, I can see your issue. Let me think about it a bit.
[Windows Mobile Development and Hacking General] l3v5y:
Maybe another SDAutoRun, that does the same process but copies a different config.txt file and resets AutoRun and after this has finished it calls SDAutoRun for UC.
[Windows Mobile Development and Hacking General] l3v5y:
I think I have just discovered one reason why this (SDAutoRun.exe) won't work on all ROMs. When I have AutoRun in the extended ROM, and all the relevant reg paths pointed at it, AutoRun works fine and all the apps install until SDAutoRun. I think it looks for the original AutoRun in \Windows rather than where the Registry points it to, and then fails to find it and re-run it with the new config files.
[Windows Mobile Development and Hacking General] Sleuth255:
hmmm good catch. What registry entry are you referring to?
[Windows Mobile Development and Hacking General] l3v5y:
[HKEY_LOCAL_MACHINE\Comm]
"TurnRadioFlag"=dword:0

"AutoRunCFG"="\\Extended_ROM\\config.txt"

"AutoRun"="\\Extended_ROM\\autorun.exe"

This points to the Extended_ROM and yet I still have to put a copy into the \Windows or else SDAutoRun will just pause and do nothing.
[Windows Mobile Development and Hacking General] its right:
we hope to have this soon please :eek:.

really great ideas.

keep it up.
[Windows Mobile Development and Hacking General] l3v5y:
I have managed to alter one of my ROMs to be truly UC but I'd still like the option of customization outside the basic framework of WM.
[Windows Mobile Development and Hacking General] l3v5y:
Just thought of a way of running SDAutoRun to configure twice...

SDautorun gets called, the SDConfig installs cabs etc (from the chef) and then copies another sdconfig from somewhere like "Storage Card\Cabs" to the root of the storage card and then runs SDAutoRun again, but with the Users cusomization...
[Windows Mobile Development and Hacking General] Sleuth255:
hmmm... wouldn't it be nice if we could cook in something that was "deletable" later after it was installed. This would solve the following issue:

Depending on the SD card can have unintended consequences if a user tries a different ROM.
[Windows Mobile Development and Hacking General] Sleuth255:
Damn... I knew that :o

I'll throw in a fix. Congrats on finding the first "undocumented feature". I'll have something for you to test tomorrow.
[Windows Mobile Development and Hacking General] its right:
what about this tip:

writing

xxxxx= user configuration

SDConfig= chef config (where he can locate it in the kitchen too with the exe file, and the cabs will be on the SD)

so, the idea with CFG command. i didn't test , but it should work :rolleyes:.
[Windows Mobile Development and Hacking General] l3v5y:
I tried the CFG command, but, it won't work if it's on the storage card, and it also doesn't like installing cabs that are on the storage card.

I'm special!!! Yay!
[Windows Mobile Development and Hacking General] its right:
ok, try to make the target file in the windows not in storage!!!

if it passed, it is simple to copy this txt file to windows too.
[Windows Mobile Development and Hacking General] l3v5y:
I have tried running the second config file from the windows directory (copying it there with CPY1 and CPY2, and also putting it there manually) but it will not work as well as SDConfig.txt
[Windows Mobile Development and Hacking General] its right:
so, my suggest to Sleuth255 is to let SDConfig.exe reads SDConfig.txt and something else :rolleyes:.

thanks for your test.
[Windows Mobile Development and Hacking General] l3v5y:
This might be because of the AutoRun.exe that I'm using though...
[Windows Mobile Development and Hacking General] its right:
try the attached one which is located on the 1st post.

it supports this command (if yours doesn't)
[Windows Mobile Development and Hacking General] Sleuth255:
Hypothetical question:

What if two different chefs have ROM specific customizations on SD card? What would happen if a user loads one ROM then flashes the other? Wouldn't the wrong customizations run?

Shouldn't SD card based customizations be common to all ROMs?
[Windows Mobile Development and Hacking General] Sleuth255:
What if RUURunner could make a RAPI connection then load files after the intial flash? This way they would be contained in ruu_signed.nbh etc, loaded to /windows for customization run via interaction with XDAutoRun.exe then removed afterwards. The requirement here would be a special load that occurs after the first reset to place installation cabs that would later be removed.
[Windows Mobile Development and Hacking General] l3v5y:
If you could have a registry entry that pointed to a specific config file which was cooked into the ROM, that wouldn't be an issue although may complicate things.
[Windows Mobile Development and Hacking General] its right:
what about these steps:

- txt file for the chefs should be located on windows not in SD (so, no multiple txt files from chef to another).

- Suggest to chefs to use a folder name for the cabs as his rom name, so no multiple folders (while the first step can solve this too, if the both chefs used the same folder name will not effect, because all the customization located on txt file for every chef).
[Windows Mobile Development and Hacking General] CRCinAU:
This already exists. ROM chefs should be using preconfig.txt or config.txt - if any chef is using sdconfig.txt, then they are doing something seriously wrong.

This probably isn't required as it would be a PITA to know what to do this as a standard... ie, for my ROM, would I do the ROM name? the version? the release? Multiply this by how many ROMs are available, and you'll understand the issue I have with this...
[Windows Mobile Development and Hacking General] l3v5y:
Whilst I agree in principle, the ability to install things, and to change what is installed without reflashing a ROM or re cooking the ROM is incredibly useful. Using SDConfig allows me to have different apps install without wasting memory on the device, and also to troubleshoot and test these apps.
[Windows Mobile Development and Hacking General] CRCinAU:
There is nothing here that as a chef is required to be in the SDConfig.txt. The SDConfig should be for the USER. As a chef, you should stick to preconfig.txt or config.txt. That is the defined boundary for development of ROMs vs the whole idea of user customisation. That being said, I don't see any issues with chefs distributing packages that can live on an SD Card and come with a pre-defined sdconfig.txt.

If I would like to see any major improvement in the whole SDconfig scheme, it would be that the SDConfig program checks the lines in the SDConfig.txt file - and then verifies line by line that the files being referenced exists. If the file exists, it builds a new \Windows\SDConfig.txt with existing files.

This allows me as a ROM chef to distribute packages that has the required CAB file, and an SDConfig.txt that is the same for ALL my packages.

This means that if a user wants to add on VoIP options, they copy the CAB to the location, and it'll work because of the SDConfig references it - while ignoring the 10 or so other packages that the user doesn't want - and therefore don't exist on the SD card.

That way - the user experience is "put cab file x in directory y to install feature z". Simple. Easy. Effective.
[Windows Mobile Development and Hacking General] l3v5y:
Just had an idea:

Before the user runs the RUU, a small program (similar to the XML Config program in the user thread) takes the "chef autorun" config text and combines the SDConfig text with it to give a single config file renamed to "sdconfig.txt" and placed in the storage card. At the end of the config file, a CPY1/CPY2 setup is used to copy the User SDConfig file back to the root of the storage card which over writes the modified one.

This allows a chef config file to be changed if a bug is found in one of the cabs without a reflash, and still allows the user to use UC correctly.
[Windows Mobile Development and Hacking General] MCEITLIN:
Trying to Cook a new ROM to install TNT

Sorry everyone, this is new to me! I mean cooking a ROM. I was trying to do the following:

" User Customization is a config.txt file that's located on an SD card which can install cab & xml files located there too! Think about it: this gives anyone who loads your rom the ability to automatically install their preferred apps/settings as part of customization. Here's how to make your next ROM UC capable:

> Cook the attached SDAutoRun.exe into \windows

if AutoRun.exe isn't already in \windows then place a copy there too. Note: some devices don't have a compatible AutoRun.exe. If you have issues, try the attached version.

> Replace the "RST: Reset" line in config.txt with "EXEC: \windows\SDAutoRun.exe"

The thing is a copied the autorun file to my \windows directory but when flashing the ROM it was gone and the original ROM 6.0 Dopod was installed.

I figure I have to cook a new ROM to include autorun in it so it runs right after flashing, but I have no clue on how to do that? How can I make autorun run right after flashing the ROM? Or how can I make SDautorun run right after flashing the ROM? I don't have a registry editor to lax the security!

Thanks
[Windows Mobile Development and Hacking General] ervius:
Hi all, for who uses my rgu-2-xml, new version was born... solved a big-bug...

here:

http://xdaforums.com/showthread.php?t=386677

bye!
[Verizon Samsung Galaxy S 4] Atleragirl:
SCH - I545

5.0.1

I am living in NZ trying to use this phone with carriers over here. I'm able to pop in my carriers sim, and change networks to get service but i can't use my phones data. Will i need to root my phone to be able to use my own sim (to its full potential) or am i missing something?

All help would be appreciated, and if it happens to be the road of root, some guides would be nice!

Thanks
[Moto G4 Plus Questions & Answers] shish2307:
I can not open bootloader in my moto g4 plus and its not even booting...i tried to press the power key but nothing is happening...and i am sure that battery is not dead...plz help
[Moto G4 Plus Questions & Answers] strongst:
Please give some more details, look at the other existing threads with the same topic in Q&A forum and find your answers https://xdaforums.com/moto-g4-plus/help/please-help-moto-g4-plus-dead-m-dead-t3663388
[Moto G4 Plus Questions & Answers] Dar Samir:
check out this link this will help u for sure

https://xdaforums.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
[MX Player] psyblade:
Mx Player used to play m3u8 files very well, but after the 1.9.x update, it can no longer play this kind of file anymore. Well, I bought Mx Player Pro just because of this function, it is very important to me. So the problem with m3u8 files really bothers me alot.

I have sent reports to mxvideoplayer@gmail.com, 2 times, but got no replies. OK, fine. Perhaps Mx Team was just too busy and had no time to reply.

I've been looking forward to the new version since then, hoping this problem would get fixed.

And after 1 month of waiting, today, there is a new update. I immediately hit the update button, thinking the problem is gone by now.

But it still exists!

Well, in sum, please fix it. I'm too tired of it now.
[MX Player] Thirumalai.K:
We apologize for the inconvenience caused to you. We are receiving a huge number of emails. Sometimes, It's very difficult to reply to everyone as most of them lack the information.

Are trying to play the m3u8 from your local storage? We have received few similar reports like that & our developers are already looking on it. We will try to fix it ASAP.
[MX Player] psyblade:
Thanks for your reply.

Yes, that is the problem I am suffering. MX Player can't play m3u/m3u8 files from local storage.

Hope it will get fixed soon.
[MX Player] psyblade:
m3u8 file problem still exists despite v1.9.7's changelog said it was fixed. I think if you guys can't support m3u8 files well enough, you guys should make an own playlist function for MX Player.

And worse than that, now Mx Player can't play rtmp links. It said "Support for this video codec is missing from your device". It used to play RTMP link perfectly at v1.9.5 or below though.

I'm done. Reverted to v1.9.5 as a temporary solution.
[MX Player] Thirumalai.K:
That's wired.

We have fixed some m3u8 related issues.

MX Player only supports HLS compliant m3u8 files. Support for custom m3u8 files are limited.

Can you share the m3u8 file here?

It will be better if you can provide a sample rtmp link as well. If you are bothered about sharing, you can send the sample m3u8 file & rtmp links by a private message.
[MX Player] DualJoe:
But they worked before (like these):

http://www.wdr.de/wdrlive/media/hls/1live.m3u8

http://zdf_hds_de-f.akamaihd.net/i/de13_v1@147090/index_3056_av-b.m3u8?sd=10&rebase=on

rtsp://mpv.cdn3.bigCDN.com:554/bigCDN/mp4:bigbuckbunnyiphone_400.mp4

Every line is copied into a separate txt file with m3u8 suffix.
[MX Player] psyblade:
My m3u8 files are like yours.

Just a m3u8 file that contains a link, nothing complicated, such as:

http://184.72.239.149/vod/smil:BigBuckBunny.smil/playlist.m3u8

or

rtmp://210.245.60.242/nghehevov1/vov1

Here is the links to download

https://www.dropbox.com/sh/4gvgy10q1fxx8vh/AADN3_shtu729VYPa3KxcTXPa?dl=0

I'm temporarily using the pirated MX Player v1.8.16, and it plays those m3u8 files perfectly fine.

But starting from v1.9.x, it no longer works.

I have read the logs and seems that starting from v1.9.x, MX Player no longer allows network links in M3U8 files like before. It still accepts and plays local links (such as this) though.

/storage/722B-130A/DCIM/Camera/VID_20170916_123236.mp4

Also, now Mx Player can no longer play RTMP link. I have sent you guys a bug report through email several days ago. Not sure if you guys have read it or not.

Here is the RTMP link.

rtmp://210.245.60.242/nghehevov1/vov1

But if I use MxPlayer v1.8.16, it plays perfectly fine. Note that this rtmp link is audio only.
[MX Player] Thirumalai.K:
We have pushed a new fixed version 1.9.8 to Google Play Beta testers. Can you guys check whether it fixes your issue or not?
[MX Player] psyblade:
The problem of m3u8 files still remains. But at least, the problem with rtmp links is fixed.

I found this from the log file.

I think MX Player can't play it just because MX.FFmpeg automatically rejects m3u8 files that contain HTTP or RTMP links for some reason, not because it can't play. If I paste the link to Network Stream and play it, MX Player can play it perfectly though . If I remember it right, there was an update of MX.FFmpeg at v1.9.2. There must be something with it.

Error report

https://www.dropbox.com/s/jkzvgk2o6gpg5jy/report_2017-09-19_103117.zip?dl=0
[Moto E Original Android Development] DarkElf:
Paradox Kernel​

#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Hello everyone...This is my first step towards developement...I created Paradox kernel for learning and after adding many features, its time to release it to community...Paradox kernel is based on latest Lineage 14.1 sources and supports LineageOs 14.1 and all other lineage based Aosp (7.x.x) roms...My moto is to make a stable and balanced kernel having better performance as well as good battery life with usefull features :):)

Once again, Paradox kernel is for NOUGHT ONLY (LINEAGE 14.1 and AOSP 7.X).

Features

* Based on latest lineage 14.1 sources

* Compiled using Linaro 5.4.1 toolchain

* Added cpu governores

-Impulse

-Smartmax

-lionheart

-ondemandplus

-wheatly

* Added i/o schedulors

-Sio

-Tripndroid

-zen

*Wake gestures (DT2W,S2W,Pocket Mode)

* Faux sound 3.4

* Franco Fsync control (enabled by defualt)

* KCAL colour control

* Powersuspend and LCD Notifier

* Power efficient workqueues

* Optimised crypto routines

* Push readahead to 512kB

* Optimized square root algorithm

* Lz4 compression

* Many Zram tweaks

* Disable crc check for faster performance (upto 30% increase in i/o operations)

* Blocked some wakelocks for extra battery life

* Added many tcp controllers

default : westwood

Many more features to be added...so stay tuned

Installation Instructions

Note:- If you are coming from other kernel, flash your rom before installing it(dirty flash will work too) to avoid any conflicts.

Also if you are updating to latest release of paradox kernel,you must flash your rom before flashing latest paradox kernel.

Steps to flash :-

- reboot to twrp recovery

- clean cache and dalvik cache

- flash paradox zip

- reboot

- enjoy

Downloads

For download link and changelogs have a look at post #2

Credits

@LineageOs @google @savoca @faux123 @fransiscofranco @rainforce279 @hurtsky @xda community

XDA:DevDB Information

Paradox kernel, Kernel for the Moto E

Contributors

DarkElf

Source Code: https://github.com/Akshay7273/MotoE

Kernel Special Features: DT2W,S2W,KCAL colour control

Version Information

Status: Stable

Current Stable Version: R4

Stable Release Date: 2017-10-10

Created 2017-08-27

Last Updated 2017-10-10
[Moto E Original Android Development] DarkElf:
Downloads + Changelogs

Downloads

Download latest release :- Paradox Kernel R4

Changelogs

*Paradox R4 10/10/17)

Merge latest lineage changes

Optimized ARM RWSEM algorithm (RWSEM implementation for ARM using atomic functions)

Lock the initial TCP window size to 64K

Optimize copy_page for modern ARM platforms

Entropy : random write wakeup thresh to 256)

Selinux : permissive

Silence some selinux logs

Older changelogs:-

*Paradox R3 (04/09/17)

Added Ondemandpus and Wheatly cpu governors

Added Conservative gpu governor

Enable lionheart cpu governor (forgot to enable in last update)

Revert KCAL commit (it was already integrated,i readded it by mistake and thus some conflicts occured...But now its fixed)

zram: set default compressor to lz4

lib/int_sqrt.c: optimize square root algorithm

init: don't force selecting debug

mm: push readahead to 512kB

proc: much faster /proc/vmstat

block: scheduler: add ZEN

USB: android: Fix memory leak in mass_storage_function_init()

sync: don't block the flusher thread waiting on IO

writeback: fix occasional slow sync

writeback: fix race that cause writeback hung

readahead: make context readahead more conservative

its not over...many other patches

*Paradox R2 (30/08/17)

Switched to Linaro 5.4.1 toolchain

Remove anykernel method and using new template zip (thanks to [MENTION=5250109]rainforce279[/MENTION])

Added wake gestures :-

DT2W

S2W

Pocket mode for dt2w

Added KCAL colour control

Added lionheart cpu governor

Added fsync on/off support

Enable fsync by default

arm: crypto: Add optimized SHA-256/224

crypto: arm/aes update NEON AES module to latest OpenSSL version

sched: cpu_power: Add controls for sched features

sched: archpower: disabled by default

bfq-sched: Forcefully lookup entities when the cache is inconsistent

some more patches

*Paradox-R1-08/26/2017

initial release

merged latest lineage 14.1 sources

added cpu governors :- impulse,smartmax

added i/o schedulors :- sio,tripndroid

added faux sound 3.4

added powersuspend and lcd notifier

disable crc check (faster performance)

added power efficient workqueues

block some driver wakelocks

added many tcp congestion controllers

set default tcp controller to westwood
[Moto E Original Android Development] DarkElf:
FAQ section

FAQs

[Q] This kernel works in stock rom?

NO, this kernel is based on lineage sources and works on Lineage 14.1 and all other AOSP 7.x.x roms.

[Q] Got errors during flashing/after flashing this kernel...what to do now?

Well if you are coming from any other kernel you must dirty flash your rom once to avoid any conflicts.After dirty flashing your rom flash this kernel and you won't face any problems.Also use twrp latest version (recommended)

[Q] I am having some random reboots/bugs...what to do?

Just report it with last_kmsg which is located in /proc/last_kmsg or in case of any bugs report it with logcat and proper information about how you encountered it.I will do my best to resolve it asap.

[Q] how to tweak this kernel for advanced features (like dt2w on/off,s2w on/off or changing cpu governor or i/o sechdulors) ?

Use kernel adiutor app for playing with the kernel and change the settings according to your own taste.

[Q]How to ask for any features ?

You can ask in this thread...if I find feature useful and logical then it'll be added...I would appreciate if you link me with commit. It's really hard to dig in the sources and find the exact commit.
[Moto E Original Android Development] Rajendran Rasa:
Double tap to wake is there ??
[Moto E Original Android Development] DarkElf:
No i have not added it yet...but i am planning to add it soon...many more features are going to be added
[Moto E Original Android Development] DarkElf:
Update R2

Hello guyss...here comes a big update Paradox R2.Many features have been added and many things have changed to make it better.

Remember to dirty flash your rom before installing this update

*Paradox R2 (30/08/17)

Download here

Changelogs

-

Switched to Linaro 5.4.1 toolchain

Remove anykernel method and using new template zip (thanks to [MENTION=5250109]rainforce279[/MENTION])

Added wake gestures :-

DT2W

S2W

Pocket mode for dt2w

Added KCAL colour control

Added lionheart cpu governor

Added fsync on/off support

Enable fsync by default

arm: crypto: Add optimized SHA-256/224

crypto: arm/aes update NEON AES module to latest OpenSSL version

sched: cpu_power: Add controls for sched features

sched: archpower: disabled by default

bfq-sched: Forcefully lookup entities when the cache is inconsistent

some more patches
[Moto E Original Android Development] Luis Infante:
after installing it my screen looks green and calibrated the colors and returns to look green
[Moto E Original Android Development] DarkElf:
Luis actually its LiveDisplay conflicting with KCal...turn off live display from settings>> Display >> LiveDisplay ...after that display willbe normal. Thanks for trying my kernel by the way...
[Moto E Original Android Development] Luis Infante:
Ok i Will try it but i like use live display, another solution? And s2w is not working
[Moto E Original Android Development] DarkElf:
Edit :- Ok guyss...i figured out the real issue...it was a tiny mistake by me and that's why when kcal colour was caliberated it automatically turned back...All is well now nd i will be updating it in an hour...this time the changelogs is gonna be huge.

S2W is working without any issues...its just disabled by default...if you want to use it then enable it first by kernel adiutor app.