yashsingh1/xdaforums huggingface dataset:
[Android General] kirito9:
It's still some success :), progress rather. What does the log say after extracting the files from the system. Also is your ROM in the new format (system.new.dat)? I can't say for sure if everything is being flashed or not without checking the log but if it says script succeeded or something like that at the end then most of the time, it has flashed everything.

The problem here now could be the boot.img of the ROM or your vendor tree not having compatible files. You said you built with the kernel source right? Does that defconfig work for you because it's not the one I use when building my standalone kernel. Try replacing the boot.img at the compiled ROM with the one from the ported CM13 and see if it boots.

The problem with the cache is twrp not finding a ROM so yeah, that's why it takes so long to wipe. You can set "Always use rm -rf" in twrp settings to speed up the wiping.

I also checked your commits and they're fine, nothing is wrong there :good:.
[Android General] kirito9:
Can I see the build.prop of your phone? Usually found in /system. Use adb to pull it.
[Android General] Charles IV:
OK, thanks, I'll upload the log when I get home.

Can i extract the boot.img from the cm 13 port zip?

I'll also try the cm port with my boot.img and see what happens.

I'm surprised there is so little source code for the device, considering how many builds there are.

You also mentioned vendor files, all I did is clone the 5010D, and replace all the 5010D's with 4034X, so there may be something wrong.

Which defconfig do you use, the pixi4_4_8g_1g_defconfig? What's the difference between the two, and the _debug versions? My device has 4gb storage and 1/2gb ram (I think, but it's not 8 and 1), so I used the pixi4_4_defconfig.
[Android General] kirito9:
[Guide][Unpack ROM/ROM_0 file from SPFT backup]

This guide was created by [MENTION=8022358]ludia2210[/MENTION]. The program was made by the Russian developer vvaaavv.

DISCLAIMER:

Rooting your phone and using custom Recoveries and ROM's have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.

Basic computer skills are required and minimal knowledge about the phone and phone utilities also.

Make sure that whatever you do, you are doing it at your own responsibility.

Requirements

A windows PC

ROM_0 backup from SPFT

MT65xx scatter file

WwR_MTK_v2.20

Instructions

1. Download the program from the attached files and extract it.

2. Open WwR_MTK_v2.20.exe

Following the screenshot attached below :

3. Load ROM file

4. Load scatter file

5. Select folder to extract(convert)

Note: Ignore any errors about data partition.
[Android General] kirito9:
Yes you can extract the cm13 boot.img from the zip.

Try using the 5010 vendor files first then if it boots then you can fix the bugs by replacing the ones from 4034 with the ones in 5010.

Ahh, I thought all Pixi 4-4's had the 8gb 1gb configuration. So are you saying you can only use 2gb for internal storage and you have 512MB ram? If that's the case the you are correct in using the pixi4_4_defconfig. Try the swapping the boot images first to see if that's the issue. If that is the case then something isn't missing when compiling the kernel with the ROM.
[Android General] Charles IV:
just installed cm13 port, then my cm13, then cm13 port boot.img and 'Boot', and it's on the cm bootanimation

And now it's booted!!!

ps i only wiped cache, nothing else

---------- Post added at 03:32 PM ---------- Previous post was at 03:21 PM ----------

After i was trying out different recoveries, i noticed i couldn't move many files into internal storage from the sd card.

When i booted cm13 port i got a warning saying there was very little space available (it says: Not enough storage for the system. ...), and when i flashed my own cm13, i checked in settings and i only had total 775MB, rather than 3.1 GB i had when i first flashed cm13 port.

I'm lost ... and annoyed
[Android General] kirito9:
So the problem is indeed the boot.img that the ROM built from the kernel. Can I see your compile log for the ROM? As in when it's building. It could be something not being added to the boot.img. Also can I see the boot.img that was compiled?

You tried to move the files while in CM13 or in the recovery that you tried? You may not have enough storage for system because you installed both CM13 port then your own build without wiping (if I read above correctly). Unpack the CM13 and take out the boot.img, unpack your own build and remove that boot.img. Place the boot.img from the CM13 port in the your build and repack. Make all the necessary wipes and try to boot again.

Also, you didn't answer from before. Is your ROM in the new format (system.new.dat)?
[Android General] Charles IV:
i dont know what you mean by new format, where woul di find system.new.dat, or what would i find instead

I've also done full wipes, but i only have 775MB total, when i look in settings.

I tried moving files when in recovery, because i didn't have an os installed

Ive attached the boot.img, I'm also compiling again now, but the terminal cant go as far back as brunch 4034X, so when it's finished I'll pastebin all i can (hopefully enough). Strange, because i didn't have this issue when building for grouper, i could fit repo sync, . build/envsetup.sh and brunch grouper into terminal, plus some extra.

also, when repacking, do i just simply right click the folder, compress and select zip?
[Android General] kirito9:
Go to profile preferences and remove the limit for scrolling.

If you don't know what is the system.new.dat format then do not worry about it. If you knew then I guess you would've asked about it. It was probably disabled in the BoardConfig for the 5010. 775MB for the internal space?

Select all the files and then zip them together with right click etc etc.
[Android General] Charles IV:
here's the pastebin (had to use zero bin - too long for pastebin)

yup, 775MB internal storage

also, it's still coming up as two SIM's, even though i have one and have corrected this in system.prop
[Android General] kirito9:
Change

persist.radio.multisim.config=dsds

in system.prop to

persist.radio.multisim.config=none

The 775MB is an error in the device tree...somewhere.

Edit: The log doesn't give the entire build..
[Android General] Charles IV:
what about

persist.gemini.sim_num=2

?, change to 1?

I'm not sure it's in the device tree, i had the problem on the ported cm13 before i successfully flashed this.
[Android General] kirito9:
Oh, I thought it was a new error..because of the new ROM. Yes, change that to 1 as well.
[Android General] Charles IV:
well it is new, but i got it before the ROM (although i was trying to flash, so it could be possible)

maybe something went wrong with wiping, shall i re format or something like that? (I'll see what TWRP can do)

OK, in wipe, i can change or repair file system, or in advanced, i can partition sd card (which includes internal storage in it)

Shall i try repair file system with data selected, and then if that doesn't work partition sd card, or different order or what

edit (again):

ive clicked repair or change file system, with data selected, it says that size is 774MB, I'll try the resize file system option

update (fixed - i think):

resize didn't work, but change, and then ext4 did, size is now 2255MB
[Android General] kirito9:
That's a fix I never heard of. Nice find. Try building the ROM using the prebuilt kernel so in future builds you won't have to keep using the boot.img from the CM13 ROM.
[Android General] Charles IV:
i think it's because a wipe didn't work, maybe it lost power half way through?

where would i get the prebuilt kernel? The one on the device tree would be for 5010D, and i replaced it with one i built anyway.

I'm still determined on finding a fix

also cache is still taking ages to wipe

edit:

thinking about repo sync time ...

can we remove all the qcom packages, or do we use them. I think the hardware isn't qcom, but I don't know

... and also 'ti' and intel?
[Android General] kirito9:
It should be safe to remove the qcom packages.

Use rm -rf for slow wiping of cache.

Extract your stock boot.img with carliv image kitchen and rename boot.img-kernel to kernel.
[Android General] BartGuy:
Hello, i tried to root my alcatel pixi 4 (5) (tcl 5045x) i followed all steps by [MENTION=7896782]ghoppa[/MENTION] but i got stuck at step 8 because cwm couldnt find my .zip file(which i might've put in the wrong place, i pressed reboot but it got softbricked(i can still enter cwm tho) i tried doing a factory reset but it didn't work as well...... any ideas on what i can do to unbrick it?(i checked google but i mostly got confused or it didnt work)
[Android General] Charles IV:
Have you tried using other recoveries? (If there are any others available)
[Android General] Charles IV:
I've just ran into the reboot problem I had before.

I think it's an issue with the kernel not having the minfree or panic at correctly. Maybe it was built for 1gb ram, and it's running out.

Do you know if the source code is available fit the cm 13 port? Or if we can get it?

Another problem I've never seen before: now I'm using gapps, after a reboot, developer options 'are not available for this user', even though there is only one user.

I have to write data and start again, but as soon as I reboot after that, they aren't available.

The options enabled (like advanced reboot) still work
[Android General] kirito9:
Change your recovery to twrp and try to root again.
[Android General] kirito9:
The source code? What source code? There's an option to disable multiuser if that helps? Write data?
[Android General] Charles IV:
Sorry, I use guesture typing.

When I say source code, I mean like the device tree etc.

I've only got one user, but I'll see if I can find that option.

I mean wipe data, not write. Careless typo.

Also, I think the reason the kernel isn't working is that it is stock not cm. Importing my knowledge from grouper, the aosp 7 kernel for grouper is compatible with los14

I would assume the same here, but I also remember m kernel. It's latest kernel supported aosp 5, but not cm12 (you had to use an older version for cm12), I think metallice removed the cm12 ramdisk, or something. But on his github, the only change was the defconfig changing the version number, and I didn't have the time to search around finding a ramdisk commit, if it was even in the kernel tree

Edit:

I think I'm being logged in as guest user. I can't find the users menu in settings, dies this mean the ROM doesn't have users enabled? Despite logging me in as guest?
[Android General] Charles IV:
I am now getting a build error that i didn't get before. I originally blamed it on jack, but the usual

export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4g"

fix didn't work. I then blamed it on removing qcom, and then the sim thing, but i still get it.

It always seems to come down to this error:

make: *** No rule to make target '/media/charles/HDD/android/4034X/out/target/common/obj/JAVA_LIBRARIES/tcmiface_intermediates/classes.jack', needed by '/media/charles/HDD/android/4034X/out/target/common/obj/JAVA_LIBRARIES/okhttp_intermediates/with-local/classes.dex'. Stop.

the full log is on github gist
[Android General] BartGuy:
thank you, worked now with twrp :D
[Android General] mrblankslate1138:
Here it is

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=MRA58K

ro.build.display.id=3DHE-UDE1

ro.build.version.incremental=v3DHE-0

ro.build.version.sdk=23

ro.build.version.preview_sdk=0

ro.build.version.codename=REL

ro.build.version.all_codenames=REL

ro.build.version.release=6.0

ro.build.version.security_patch=2016-08-05

ro.build.version.base_os=

ro.build.date=Sat Sep 3 00:31:12 CST 2016

ro.build.date.utc=1472833872

ro.build.type=user

ro.build.user=xf_zhong

ro.build.host=persauto-87

ro.build.tags=release-keys

ro.build.flavor=full_pixi4_4_8g1g-user

ro.product.model=A466T

ro.product.usb.model=alcatel Lume

ro.product.brand=TCL

ro.product.brand1=Orange

ro.product.name=A466T

ro.product.device=PIXI4_4TF

ro.product.board=

ro.product.orangecodename=NA58083

# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,

# use ro.product.cpu.abilist instead.

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product.cpu.abilist=armeabi-v7a,armeabi

ro.product.cpu.abilist32=armeabi-v7a,armeabi

ro.product.cpu.abilist64=

ro.product.manufacturer=TCL

ro.wifi.channels=

ro.board.platform=mt6580

# ro.build.product is obsolete; use ro.product.device

ro.build.product=PIXI4_4TF

# Do not try to parse description, fingerprint, or thumbprint

ro.build.description=full_pixi4_4_8g1g-user 6.0 MRA58K v3DHE-0 release-keys

ro.build.fingerprint=TCL/A466T/PIXI4_4TF:6.0/MRA58K/v3DHE-0:user/release-keys

ro.build.characteristics=default

# end build properties
[Android General] kirito9:
If I understand what you're asking then these are the links to the source code on which the CM13 port was based on after being built.

Doogee X5 device tree: https://github.com/MediatekAndroidDevelopers/android_device_doogee_x5

Doogee X5 vendor tree: https://github.com/MediatekAndroidDevelopers/android_vendor_doogee_x5

The kernel by itself can work but the boot.img is what contain the ramdisk which is being loaded along with the kernel to boot a device. The kernel itself cannot be stock in this case as when the ROM is being built, CM13's ramdisk is injected into the boot.img along with the kernel. What was done with your grouper was updating the kernel base to support LOS14 as the stock kernel probably didn't support it. This isn't the case for the Pixi 4-4 as it has the 3.18.19+ MM kernel and CM13 is MM.

If however you were to boot LOS14 on the Pixi4-4 which you intend to do. You would have to make patches to the selinux of the kernel to boot LOS14 and then you can say that the kernel isn't stock but a modified version.

There should be the option to use multiuser in settings :/.

I see it defined here so something else must be wrong.
[Android General] kirito9:
Tried make clean?
[Android General] kirito9:
Your device seems to be a clone of the Pixi4-4. Use the recovery files for the 4034.
[Android General] Charles IV:
I think I did, but I think I may have been a bit too aggressive with removing qcom, and after a repo sync it's working.

I'll continue trying with and without to see if it is qcom.

---------- Post added at 09:22 PM ---------- Previous post was at 09:03 PM ----------

Nope, shut up Charles, don't speak to soon. I reversed the SIM commits on my pc, and it worked, I edited then in and it worked, I forgot to make clean in between, so I did it again and it didn't work. At a quick glance it's a different error, but maybe not. I'll get the log, but I think it's a problem with the commits.

---------- Post added at 09:29 PM ---------- Previous post was at 09:22 PM ----------

no, shut up again, this time it is a java/jack problem
[Android General] smwfreak:
Hello can somebody tell me this, I have a Alcatel pixi 4 5045a Mt6735m you guys have a custom ROM of the Alcatel pixi 4 5045 Mt6735 with no A at the end of 5045 and no M at the end of the mt6735 I wanna know if I can still port that custom ROM to my phone?!
[Android General] kirito9:
Just realizing this, why are you building with jack on CM13?
[Android General] smwfreak:
Hello there. Can you guys answer this question for me ...OK I have a Alcatel pixi 4 5045a mt6735m and I need a custom ROM for it, you guys have a custom ROM similar to what I am looking for it is the Alcatel pixi 4 5045 mt6735 this doesn't include the A at the end of the 5045 and the m at the end of the mt6735. Can I port this to my phone?!?
[Android General] kirito9:
No need to do extra porting, flash directly. Make a backup before flashing. Don't flood the thread with double posts.
[Android General] Charles IV:
that's a point:confused:

I'm probably not, but the command to fix jack worked all the same

also thanks, the thing to fix dual sim worked
[Android General] kirito9:
Hmmmm ok.
[Android General] jie_gonza:
Hey there, i think theres a bug on camera. Picture look like have red / pink filters & front flash doesn't work. Do you have any idea how to fix this?. And some game app doesn't work properly like Mobile Legends Bang Bang. I can open & play it for a few second then it closed. No force close notice or something like that. Hope you guys can fix this:(
[Android General] Charles IV:
ok, ive tracked down my current build errors to me removing qcom, so im trying to identify what exactly is breaking the build.

meanwhile, any ideas as to why the kernel im building isnt working, as the cm13 port isnt working properly for me (running out of ram and rebooting), and as i do want to eventually build los14, i need a working kernel tree
[Android General] kirito9:
Are you still trying to build in the ROM and boot or standalone? AFAIK the source that I uploaded works.
[Android General] kirito9:
Copy these libs from your stock ROM system/lib folder and replace them in the ROM you are using :

libfeatureio.so

libcam.paramsmgr.so

libdpframework.so

libmtkcamera_client.so

Check your ram management when using the game, the ROM may not be optimized for multitasking...
[Android General] kirito9:
Check out this link for auto porting ROMs - Baa's Android Kitchen - Auto Porting Tool for MT6580 Kernel 3.18.19. Don't forget to say thanks if it works for you.
[Android General] Charles IV:
Yup, I'm trying to build the whole ROM and boot it.

Anything I should look for on the source code you uploaded, I assume it doesn't work for the pixi 4 4 as is.

also, as to the jack thing, I'm building now, and i can see Building with Jack .... whatever.jack'

Strange

One last (probable not last though) thing, is there a way to extract the kernel tree for a boot.img? I was sure i read somewhere there was a tool or two to do it. Could carliv image kitchen do it?
[Android General] kirito9:
Are you building with Java 8 or 7? It works for the Pixi 4 4 as is, the problem could be you compiling with the ROM as I stated before. Try building standalone and see if it boots, that's the best way to check because I know it works.

Not possible to get a kernel tree from a boot.img. What you can probably do is reverse engineer the zImage and collect information from your device but that's not necessary since we already have the kernel source and your device may just need a bit of tweaking.

If you can, take your stock build.prop from /system and upload it to me. I'd like to check it.
[Android General] Ridertyy2016:
Alcatel 5045T

Can I use spft rom and other Alcatel Pixi (5) rom on my Alcatel 5045T?
[Android General] Charles IV:
ok, ill build a boot.img by itself and try flashing it.

as to the build.prop, do you want me to pull the one currently being used, on my cm13, or flash stock and then pull it?
[Android General] kirito9:
Flashing stock and pulling it would be best or if you have the stock recovery that is truly your stock recovery for your Pixi4-4 you can upload that as well.
[XDA Assist] owenrg:
Alright, this issue has gone on long enough! The issue is a little more complicated than just not receiving group mms from iphones. Here's the deal:

iPhone user 1 and iPhone user 2 have the exact same settings under "settings/messaging"

imessage ON

Show contact photo: ON

Read receipts: OFF

MMS: ON

send as sms: OFF

group messaging: ON

However, I get picture messages from user 1, but not user 2. We have a family thread with 6 iphones and 3 android devices. I thought that I would get all text group texts (messages with just text) but I just learned that I don't even get all those. So there are iphones i only get text from, iphones that i get texts and pictures from, and iphones that i don't get anything from. This seems horribly inconsistent and wondering what the heck is going on!

My next step is to have iphone users delete the android contacts (however many duplicates there might be) and then re- add the numbers. But in the meant time, if anyone has any solutions/suggestions I'd love to hear them.
[XDA Assist] Trafalgar Square:
Hello and thank you for using XDA Assist,

sorry for the delay!

Please ask in our Android Q&A section. Your device don't have a device specific forum:

Android Q&A, Help & Troubleshooting

Good luck!

Trafalgar Square

XDA Assist
[Samsung Gear S2] parshakov:
This thread is no longer updated, use this link instead: https://xdaforums.com/gear-s3/themes/fitness-apps-speed-pace-heart-rate-t3709791/

This app is similar to Always-On Speed, but instead of speed it shows pace, which is more useful for runners. Here is the full description:

This application shows time and your pace while keeping the device awake. It does not log your activity. Please read the information below before using the app.

Make sure that GPS is enabled before starting the app. In order to turn on GPS, start or start and stop a workout in the S Health app or enable GPS manually on your smartphone.

• The app cannot enable GPS on your phone automatically.

• The app is only as accurate as your phone's GPS.

• Touch the speed indicator three times at an interval of at least one second to change the unit of pace (min/km → min/mi). The app will remember your choice next time you launch it.

There are several features that reduce power consumption (currently at ~17% per hour):

• The rotating bezel on the Gear S2 can be used to adjust the screen brightness. Note: in bright sunlight the brightness level locks at 100% and cannot be adjusted.

• Only one type of subpixels is used at a time, either red, green or blue.

• As soon as you stop moving, the device will start vibrating every 10 seconds. The app will close automatically after 1.5 to 3 minutes of inactivity.

Features that prevent screen burn-in:

• Numbers move up and down the screen.

• Tap the time indicator to change the font color from green to alternating red and blue. Note: red or blue text has very poor readability in bright sunlight.

• Font size changes.

Please "like", rate, comment!​

[IMG="Pace (top) and time (bottom)"]http://wildrats.ru/Ilja/Screen-20160504193438.png[/IMG]

[IMG="The unit of pace is shown every 10 seconds and can be changed"]http://wildrats.ru/Ilja/Screen-20160504193440.png[/IMG]
[Samsung Gear S2] parshakov:
Updated the app to show the average pace calculated for the last 60 seconds.
[JASJAR, XDA Exec, MDA Pro ROM Development] sebastianmc:
Hello friends! the Old phone ring only comes in official wm...! Could u post it to us?

Thx a lot!
[JASJAR, XDA Exec, MDA Pro ROM Development] shlomki:
Jwright's new rom has it too, but there you go:
[JASJAR, XDA Exec, MDA Pro ROM Development] sebastianmc:
Thanx for ur help Bro! :) :p :D
[IDEs, Libraries, & Programming Tools] legion140:
Hi.

Sorry for that thread here, but i just didnt know where to place it.

Im looking for an app for "quick klick button" which will tap the screen if i click the button.

Ps sorry for my English
[X Play Q&A, Help & Troubleshooting] ronak123456:
Hi guys,

Posting after a looong time on Xda i guess :p was a silent reader but suddenly from few days I'm facing this issue on my MXP.

I am using a stock ROM rooted and happy with that. not the Marshmullux or any other custom stock ROM but the Original rooted ROM.

When my battery reaches at 30% it suddenly starts to behave wierd and get's laggs! I am typing something and after sometime it will be typed. ( i don't know how to explain ). Any suggestions, except for formatting or wiping data and flash it again?