yashsingh1/xdaforums huggingface dataset:
[YU Yureka Original Android Development] sheikhrr:
This port is not completed yet, had many compilation errors. but some how i passed many errors (which i shall list them here and solutions as well )

i am seeking for developers to help me out, in order to compile it successfully.

Sources i am using

Ubuntu touch Source phablet-4.4.2_r1

repo init -u https://code-review.phablet.ubuntu.com/p/aosp/platform/manifest.git -b phablet-4.4.2_r1

Sources from CyanogenMod for tomato (kk4.4.4):

Currrent Error

----- Making recovery image ------
Copying baseline ramdisk...
DTB combiner:
Input directory: '/media/rameez/bca677b6-b13b-40fa-9aa4-9c325e685a35/new/out/target/product/tomato/obj/KERNEL_OBJ/arch/arm/boot/dts/'
Output file: '/media/rameez/bca677b6-b13b-40fa-9aa4-9c325e685a35/new/out/target/product/tomato/dt.img'
Failed to open input directory '/media/rameez/bca677b6-b13b-40fa-9aa4-9c325e685a35/new/out/target/product/tomato/obj/KERNEL_OBJ/arch/arm/boot/dts/'
make: *** [/media/rameez/bca677b6-b13b-40fa-9aa4-9c325e685a35/new/out/target/product/tomato/dt.img] Error 255
make: *** Waiting for unfinished jobs....
Modifying ramdisk contents...
cp: cannot stat ‘/media/rameez/bca677b6-b13b-40fa-9aa4-9c325e685a35/new/out/target/product/tomato/root/init.recovery.*.rc’: No such file or directory

Any Help Would Be Appreciated :angel:

XDA:DevDB Information

Ubuntu-Touch For YUREKA, ROM for the YU Yureka

Contributors

sheikhrr

ROM OS Version: 4.4.x KitKat

Based On: CyanogenMod

Version Information

Status: Snapshot

Created 2016-01-21

Last Updated 2016-01-21
[YU Yureka Original Android Development] sheikhrr:
Reserved
[YU Yureka Original Android Development] Shubhang12:
Reserved
[Nexus 5X Q&A, Help & Troubleshooting] Chetic:
Hello!

I'm hoping to transfer files as fast as the device can possibly handle. I've found some benchmarks stating that the maximum transfer speeds of the Nexus 5x flash is beyond USB 2.0 HighSpeed.

I'm using this USB 3.1 Type A->C cable: belkin.com/uk/F2CU029/p/P-F2CU029/

When connecting the device in file transfer mode (or any mode for that matter) I only see it connect in HighSpeed (2.0) mode.

I used this method to verify: superuser.com/questions/478184/verifying-usb-connection-speed-usb-3-or-usb-2

Googling turns up a bunch of results about setting the device in "(USB 3.0) Media Device" mode, but that doesn't seem to exist in Android 6.0 Marshmallow.

Any ideas or info on if the 5x is even capable of SuperSpeed transfer rates? The motherboard I'm connecting to is fairly old, even if it clearly states it supports USB 3.0 and SuperSpeed in the port I'm plugging the phone into.
[Nexus 5X Q&A, Help & Troubleshooting] Lord Yurij:
The nexus 5x/6p have usb 2.0

http://m.androidcentral.com/googles-nexus-team-answers-burning-questions-about-6p-and-5x
[Repurposing Old Devices] XDARoni:
Use Your Old Android Phone As A Dedicated GPS

Using your phone as a GPS is convenient but sometimes it's not the most practical thing. I'm driving my wife to the hospital because she's in the middle of childbirth. I'm using Google maps to navigate but I also want to stay up to date with what my friends are up to on Snapchat. I'm switching back and fourth between apps and this causes me to miss a turn. As usual, my wife starts over reacting to this. I really need to come up with a solution to all of this. How can I use my old Android phone to solve the problem? I'll tell ya.

To navigate using Google maps you need three things. You'll need a phone, a data connection and a GPS chip in your device. Your old phone will undoubtedly have a GPS chip but you're probably not going to want to activate a data plan for it. That's ok because there's a workaround.

You're going to want to use a trick that saves Google maps data for offline use. Follow these simple steps to get that done.

[YOUTUBE]lB_ZFgO7cPA[/YOUTUBE]

So now you'll be able to get directions even when you don't have any data. Just mount your old phone in your car and there you have it. You've got a dedicated GPS for free. Now all you need is a dash mount and you can find some really good ones on Amazon for around $20.

Bell+Howell Clever Grip-Pro Dash Mount

View attachment 3617177View attachment 3617178View attachment 3617179

Now you shouldn't run into any issues with multitasking on your phone while driving.
[Repurposing Old Devices] chadness:
Nice idea so your phone isn't tied up as a passenger in a car. But, please don't multitask on your phone while driving! I've seen too many people mangled and too much damage done by people who thought it was OK for them to do something like send a Snapchat while driving, because of course they are capable or aware enough of their surroundings.
[Repurposing Old Devices] Major_Sarcasm:
Whooosh!

That was the sound of the sarcasm in his post going over your head.
[Repurposing Old Devices] coldspring22:
I do use my old phone (galaxy Note 2) and ZTE blade lite as dedicated gps device on my car. Why? Because every other phone I have, gps is broken or quite poorly. That is multiple devices including LG G3, G5, Galaxy S4, Note4, Note edge, ZTE obsidian (multiple if each, some rooted, some on LineageOs others stock. I have my LG G3 on LineageOS 10 for example). GPS used to work fine on all these devices as recently as last year and one day all of them quit working or work very unreliably. GPS work very well only on ZTE Blade T2 lite and galaxy Note 2 (I have several, some rooted, some running lineageOS, various carriers) and also Galaxy S3 GPS work without exception. GPS works marginally on galaxy S7 and LG G4. Really odd thing. It appears to be related to gps chip in use? Nothing I tried on make GPS work acceptably on other phones I have worked. I tried following suggestions found on XDA, such as swapping sim card, force stopping apps using gps etc. From my experience it appears that on most older android phones, GPS quit working or working acceptably well and cannot be used as stand alone gps device any more.
[ONE Android Development] SkandaH:
Read before continue:

http://forums.yuplaygod.com/threads/15124/

http://xdaforums.com/showpost.php?p=63197935

http://xdaforums.com/android/software-hacking/wip-selinux-capable-superuser-t3216394

Requirements:

Completely stock, untouched device (OnePlus One).

Unlocked bootloader.

Rooted boot images:

cm-12.1-YOG7DAS2K1-bacon-boot-debuggable-rooted.img

Usage:

Download the rooted boot image that matches with your installed build.

Flash using fastboot:

fastboot flash boot XXX.img

Install the SuperUser manager app: https://play.google.com/store/apps/details?id=me.phh.superuser

Profit!

To take incremental OTA:

Download the stock boot image that matches with your installed build. Either extract from signed fastboot flashable zips or get from this thread.

Flash using fastboot:

fastboot flash boot XXX.img

You should be able to take & install the OTA, if /system isn't tampered previously.

Note:

The rooted boot images are based on official boot-debuggable images & super-bootimg by [MENTION=1915408]phhusson[/MENTION].

The whole thing is in alpha stage & still WIP, so expect bugs.

Not all apps are compatible with systemless root approach, so root access mayn't be visible to them.

Please provide detailed feedback to me, [MENTION=1915408]phhusson[/MENTION] & the concerned app developer.
[ONE Android Development] SkandaH:
Reserved for future v1.
[ONE Android Development] SkandaH:
Reserved for future v2.
[ONE Android Development] FlashHappy78:
I read the second and third links, but had to sign up to get the first (not with it at this time) and I'm kinda confused. What exactly is wrong with the "old way" of rooting? Is it just for things like Android pay to work or is there other benefits?
[ONE Android Development] SkandaH:
[MENTION=5408171]FlashHappy78[/MENTION]

In a nutshell, traditional rooting method modifies the /system partition. As a consequence, subsequent OTAs will fail. In case of Cyanogen OS devices, it may be easier to grab the full signed zip later & update manually, but for others they need to re-flash the stock system.img to take the OTA.

In this new approach, only the boot image is modified but /system is untouched. Thus any event/application that verifies the integrity of /system partition (like OTA, Android Pay etc.) is ready to be executed on top of the rooted device without any hitch.

If OTA contains an updated boot image, then user need to re-flash the stock boot image first which is considerably easy to re-flash than the whole system.img.
[ONE Android Development] FlashHappy78:
I've always been under the assumption that oem OTA updates usually break root anyways, plus patch whatever exploits were used to gain root (especially from OEM's like Samsung and LG), so because of that, I never take OTA updates unless they come from custom ROM devs.

Anyways, thanks for the clarification. I don't use android pay and I use only custom ROMs, so this probably isn't for me then. Thanks again mate.
[ONE Android Development] poulopoulosa:
Do you have any systemless image for CM13? I tried to find a way to change the : cm-13.0-ZNH0EAS2JK-bacon-boot-debuggable.img for myself but no luck, I will have to come back to it next week.

Do you have any links to suggest?
[ONE Android Development] hellcat50:
Flash supersu at least the stable 2.64
[ONE Android Development] SkandaH:
As suggested by [MENTION=5925270]hellcat50[/MENTION], I'll not provide any more update on this as newer SuperSU can patch the boot image on the fly.
[Moto G 2015 General] damianx5:
It would seem that the RRO layers themes do work on the Marshmallow stock ROM. After hearing about Marshmallow supporting it by default, i decided to see if it actually works on the Stock Marshmallow ROM. As far as I can tell, the only thing that doesn't work for me is the soft reboot after selecting the desired layer and applying it. :) :victory:

Update - If after uninstalling certain layers, the theme doesn't change back to normal, then using a file explorer, go to system/vendor/overlays and delete all the contents in the folder.
[Moto G 2015 General] Wani Aamir:
Will this work in moto g turbo too running marshmallow?

I read a post in x play page that using two themes same time results in bootloop
[Moto G 2015 General] damianx5:
I do not know.. It should work.. But you might want to make a backup of your rom and data in recovery before applying a layers theme.
[Moto G 2015 General] acejavelin:
This has always been an issue with RRO, if you apply some things that overlap what they do. Not exclusive to Moto X or any device, in the right combination it will bootloop, but you should be able to boot into safe mode, or via the TWRP file manager, and remove the offending APK's from /system/vendor/overlay, and reboot and the phone will be happy again.

Of course you can always backup and restore a nandroid, but layers was designed so this shouldn't ever be necessary.
[Moto G 2015 General] prasi.ram10:
Make a tutorial mate.

Make a tutorial mate
[Moto G 2015 General] acejavelin:
Lol... Tutorial? All you need is root and Layers Manager app, it doesn't get much simpler.
[Moto G 2015 General] prasi.ram10:
Hahaha

I was dumb enough to ask. ?
[Moto G 2015 General] acejavelin:
Yes and no... if you know nothing about layers my answer was a bit sarcastic, but the tutorial would be that... root and use Layers Manager app from the Play Store.

If you have more questions on Layers see: http://xdaforums.com/android/apps-games/official-layers-bitsyko-apps-rro-t3012172
[Moto G 2015 General] prasi.ram10:
Thanks

Uh

I'm not new to the rooting community. I'm only new to RRO. I've tried it on my old phone and i ended up crashing everything on my phone.. (Not moto) it was an asus zenfone. Since then i haven't tried layers. Given the fact that mm is supporting rro layers natively has piqued my interest for it, so was inquisitive abt it. Thanks mate.
[Moto G 2015 General] prasi.ram10:
One question. Is it necessary to set up busybox on rails for the layers manager to work?
[Moto G 2015 General] Jerryxl:
is RRO working fine??
[Moto G 2015 General] prasi.ram10:
Yeah no problem. It's working fine.
[Moto G 2015 General] prasi.ram10:
Rro

Working fine.

Inversion UI
[Moto G 2015 General] itfranky1:
hi,

i seem to have some problems applying the layers. after reboot nothing changes. I can't see any error message in the manager app. this is my first time with RRO, can someone help me?

thanks in advance.
[Moto G 2015 General] JackSparrow17:
Check BusyBox installed correctly or not....

Sent from my Toilet using Moto G3....
[Moto G 2015 General] prasi.ram10:
Busybox on rails

Installed busy box on rails?
[Moto G 2015 General] creative21:
you need to install busy box binaries in "system/xbin" otherwise it won't work
[Moto G 2015 General] itfranky1:
I have busybox installed. I think the problem is that can't reboot correctly. When I reboot it seems it always does a softboot. The notifications remain, the recent apps too. Also some tweaks I made on gravity box (MM) that require reboot aren't applied.

By the way, sorry for my English, I'm Italian.
[Moto G 2015 General] creative21:
i also had the same problem because i installed busybox in "system/bin" but after installing busybox in "system/xbin" layers are working perfectly. I'm also using xposed & gravitybox.
[Moto G 2015 General] itfranky1:
It worked! Thank you! I didn't read correctly the first time (missed that "x"). The Gravity Box problem is still there (as expected) but i don't think this is the right place in the forums to talk about that. I hope to find a solution soon
[Redmi Note 2 General] barome:
Seems good value, I try it ;)
[Redmi Note 2 General] barome:
[MENTION=5952980]jajk[/MENTION] : with your init.d file, performance mode seems not work, same results in antutu with balanced mode and performance mode.
[Redmi Note 2 General] fluffyboy2:
What kind of SOT are you getting? : )
[Redmi Note 2 General] jajk:
[MENTION=2923435]barome[/MENTION] these settings are hard-coding the parameters for the CPU Governors instead of using a software means of flicking between 3 predetermined setups.

Did you use a kernel tweaker to see what is happening to the CPU frequency in the stock condition, then with your own settings? Benchmarks don't really show the fluency and economy of what is happening at lighter cpu loads.

[MENTION=7014255]fluffyboy2[/MENTION] SOT is unknown and irrelevant since it depends on how hard the CPUs are running over that time. I get 0% drop overnight since removing, replacing or freezing apps that try to autostart or wakeup the phone. I am on AOSP not MIUI - that makes a big difference in the amount of bloat trying to contact home regularly. The battery drain while using the phone is greatly improved over stock. You can feel the difference in heat generated near the camera. I haven't underclocked so peak processing power should still be reachable if an app needs it.

There is no magic setting that will keep everyone happy but running 3 cores for touch boost in the stock configuration is going to eat your battery along with the failure of the interactive governor to throttle down the cpu from a high freq.

If it is not immediately apparent:

SCN_APP_TOUCH = case when screen touch detected (touch boost)

SCN_APP_SWITCH = case when switching apps (or function within an app)

SCN_APP_LAUNCH = case when opening an app

SCN_SW_FRAME_UPDATE = case when screen needs to be redrawn e.g on scrolling

I should also mention that you should not be using other scripts or software that are manipulating the same settings.
[Redmi Note 2 General] Xmister:
AFAIK the daemon that reads and interprets perfservscntbl.txt is missing from the AOSP ROMs I saw floating around, but feel free to correct me.

And a few weeks ago, I've tried using some of the perfservscntbl.txt values you are mentoning here on MIUI. The result was Battery Saver app FC (which is in connection with the MTK daemon), and the phone started using the default touchboost values from kernel (2 cores, 1326MHz)
[Redmi Note 2 General] jajk:
[MENTION=2718533]Xmister[/MENTION] I am using AOSP 5.02 ver 1.50 by vova.vafin and perfservscntbl.txt values are applied correctly on reboot. The kernel is the same one as used by the latest MIUI.

I have opened the daemon you are talking about in a text editor and the available commands are there to see in plain text. Now I have forgot what the file was called, can you remind me?

Choose your weapon: Use an app to alter settings or edit the files directly.....not both.
[Redmi Note 2 General] jajk:
I probably need to clarify since we have 2 things that interact causing much confusion:

FIRSTLY: Make sure you are not using other scripts or software that are altering the same files!!!

Start by editing perfservscntbl.txt as follows to negate its effects - reboot to take effect.

CMD_SET_CPU_FREQ, SCN_APP_TOUCH, 403000

CMD_SET_CPU_CORE, SCN_APP_TOUCH, 1

CMD_SET_CPU_FREQ, SCN_APP_SWITCH, 403000

CMD_SET_CPU_CORE, SCN_APP_SWITCH, 1

CMD_SET_CPU_FREQ, SCN_APP_LAUNCH, 403000

CMD_SET_CPU_CORE, SCN_APP_LAUNCH, 1

CMD_SET_CPU_FREQ, SCN_SW_FRAME_UPDATE, 403000

CMD_SET_CPU_CORE, SCN_SW_FRAME_UPDATE, 1

Now start with an init.d script as follows: these are the default settings from the kernel.

echo 1183000 > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq

echo 99 > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load

echo 90 > /sys/devices/system/cpu/cpufreq/interactive/target_loads

Execute the script or reboot. Now run whatever software you use to view the cpu frequencies. You should find that the cpu never settles on the minimum frequency but can get stuck on the highspeed_freq of 1183MHz. This is a big part of why the battery drains quickly.

Edit the file to read as follows:

echo 1183000 > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq

echo 110 > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load

echo 99 806000:70 1950000:120 > /sys/devices/system/cpu/cpufreq/interactive/target_loads

Reboot or execute the script. Now you should see the cpu settle firmly on 403MHz with no load and ramp up and add extra cores only when a load is applied. It should ramp all the way up to 1950MHz if you can scroll and click on things fast enough while watching the frequency. This example is on the edge of just throttling down to min freq while still climbing to 1950MHz with a moderate load. If needed or desired, increase or decrease the load values to get your desired operation. Like I mentioned in OP, the implementation of Interactive governor is flawed so don't think in terms of 0 - 100%. Confirm it for yourself!

Once you are happy with the Interactive governor action, now work on the perfservscntbl.txt. This is basically adding a short term boost frequency and extra cores under 4 different scenarios.

It supplements what Interactive is doing so what you see is a combination of both in action. If you boost to a high freq, the workload drops off quickly so less cores are on for less time. What is best for battery is something close to my example below. You will find the dominant effect is the SCN_SW_FRAME_UPDATE which almost always overrides the SCN_APP_TOUCH. You must touch an inactive part of a window without causing any scrolling to see the touchboost effect by itself. It is useful to set each scenario to a different frequency to see which one is in play.

CMD_SET_CPU_FREQ, SCN_APP_TOUCH, 1469000

CMD_SET_CPU_CORE, SCN_APP_TOUCH, 1

CMD_SET_CPU_FREQ, SCN_APP_SWITCH, 1469000

CMD_SET_CPU_CORE, SCN_APP_SWITCH, 2

CMD_SET_CPU_FREQ, SCN_APP_LAUNCH, 1469000

CMD_SET_CPU_CORE, SCN_APP_LAUNCH, 3

CMD_SET_CPU_FREQ, SCN_SW_FRAME_UPDATE, 1469000

CMD_SET_CPU_CORE, SCN_SW_FRAME_UPDATE, 2
[Redmi Note 2 General] Xmister:
Then in the newer aosp ROMs, the daemon is included.

I have a lot of experience with interactive on this phone, and I can tell that with the default timer rate, even 90 target load causes unnecessary cores to activate. If you want to set that even higher, you should lower the timer and sample time first.

Also I never had problem with reaching the idle freq.

Tapatalk|Redmi Note 2
[Redmi Note 2 General] jajk:
It is odd that the normal Linux default for go_hispeed_load is 85 but MTK set it to 99 and still have problems.

I can't get reliable idle freq at anything below a setting of 110 on Note 2 running either MIUI or AOSP. On my second phone which is a Ulephone Be Touch 3 with MTK6753 soc running 5.1.1, the same applies.

timer_rate defaults to 20000 which is Linux default.

min_sample_time defaults to 20000. Linux default is 80000.

I had a play with modifying the times instead of load but can't get a reliable outcome. Open to further suggestions?
[Redmi Note 2 General] Xmister:
Basically slowramp mode in my app sets timer and sample time to 10000, increases the timer even further in go above, disables highspeed freq (sets to 806), and sets the target loads between 90 and 100. And the default touchboost values are 806/2.

This gets about 1-2 hour extra sot for most of the users with even smoother interface,because of the faster than default reaction to load. At least with miui.

Tapatalk|Redmi Note 2
[Redmi Note 2 General] hasaan6545:
I see Gaming, QuickRamp and MIUI default in your app.

Which of them is slowramp?
[Redmi Note 2 General] Xmister:
You are using an old version. But gaming is what is called now SlowRamp.
[Redmi Note 2 General] jajk:
O.K taking another approach is to take on board what Xmister mentioned earlier and I find that increasing the timer_rate from 20000 to 60000 uS smooths out the calculated load to the point that normal load figures can be used. There must be a lot of load calculation glitching at the lower timer rate that triggers ramping up the freq as 20000 is a pretty standard default that works on non MTK phones. I also increased the min_sample_time from an unusually low 20000 to a more normal 60000 to calm things down a bit more. [MENTION=2718533]Xmister[/MENTION] did you miss a zero off your slow ramp values and mean 100,000 not 10,000?

So what I end up with is an init.d file like this:

#!/system/bin/sh

echo 1183000 > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq

echo 95 > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load

echo 95 806000:80 1950000:99 > /sys/devices/system/cpu/cpufreq/interactive/target_loads

echo 60000 > /sys/devices/system/cpu/cpufreq/interactive/timer_rate #ROM default 20000, Linux recommended default 20000

echo 60000 > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time #ROM default 20000, Linux recommended default 80000

This scales up and down nicely and reliably sits on min freq.
[Redmi Note 2 General] Xmister:
No I didn't not miss. My point was even at 20000, interactive is not quick enough to ramp up the freq. So another cores will be activated, and by the time the frequency goes up, there will be another 3-4 cores activated unnecessary, so it will consume a lot of battery.

Tapatalk|Redmi Note 2
[Redmi Note 2 General] jajk:
Tried dropping the timer rate down again but cannot go below 35000 before it will no longer sit at min freq reliably. I have a very minimal ROM with no processes running to upset this.
[MENTION=2718533]Xmister[/MENTION] what is the trick in getting min freq reliably with a setting of 10000? It seems an impossibility for me. I have 2 MTK phones with exact same behavior, one with MIUI originally, now with AOSP 5.02, the other with stock 5.1.1 so it is not an O.S version thing.
[Redmi Note 2 General] Xmister:
Well, the absolute min frequency should only be used when you are not doing anything on your phone. But in this case it's usually turned off to deep sleep.

I usually try min freq with opening CPU Spy, leaving it for 5-10 sec, and then refreshing. In this case it's usually half 403MHz, half 806MHz, which is probably due to the system doing something in background.

In my opinion (and experience) it's much better for battery that the phone sometimes uses 806 when idle (which is usually pretty rare anyway during normal usage), than it is using high frequencies with a lot of cores on some medium workload.