yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] m0han:
nodl_pmt - ERROR

trying to backup (freshly flashed stock KitKat ROM) as instructed in post #3.

"nodl_pmt - ERROR : Zero file, no space left on device!".

anyone else? see error screenshot. any solution?

edit

: many thanks, [MENTION=5186178]carliv[/MENTION], for your detailed input via pm. just another one of those kitkat woes, i see.
[Miscellaneous Android Development] lce67:
I have a new 4 day old blu studio 5.0 2 d532u...running jellybean 4.2.2. I was working on porting carlivs touch recovery when I noticed that my stock backed up recovery.fstab had different block numbers than what it was showing in block info using mtktools v2.5.3....

I did a phone backup using mtktools before I rooted and used chainfires su to root .

in block info Number=16 name=android type=ext4 device=mmcblk0p4 mountpoint=/system

in stock recovery.fstab /system ext4 /dev/block/mmcblk0p6

I was wondering do I need to change the recovery.fstab to match block number from the block info file?

I am worried to go any further..i did a cwm backup with recovery built from mtktools...but have not tried anything else...
[Miscellaneous Android Development] :
Yes, you have to change recovery.fstab mount points according to what you see in MTKDroidTools with Block Info command. The stock recovery use "secured" entries (if you take a look at the actual partition table from block info, you can see that mmcblk0p6 from stock fstab is probably protect_s ) but custom recovery doesn't have secure module to interpret those. In the end the system will be installed on the block you see in MTKDroidTools even with stock recovery.

Anyway to be sure, since you have root you can run "adb shell cat /proc/dumchar_info" in terminal and you get the partition layout from phone.
[Miscellaneous Android Development] lce67:
Thanks...adb shell list is the same as block info...

I am new to mtk devices ...LOL..

had a htc inc for years..... just decided to upgrade... totally different when it comes to dev...

and no source code..... that sucks...
[Miscellaneous Android Development] :
I know... it was the same for me at the beginning. After a HTC first contact with MTK was brutal, but now I'm used to it.
[Miscellaneous Android Development] lce67:
Worked like a charm....BLU Studio 5.0 2 D532u...

Thank You! Carliv.....:good:
[Miscellaneous Android Development] m0han:
is this your device? the os is jellybean, right?
[Miscellaneous Android Development] lce67:
yes, just got the phone..it has jellybean 4.2.2 and newer built kernel..according to built date in dev info..

i hope that it means kitkat...but not holding breath on that one..

Kernel source would be nice...i know they released newer device source,,maybe they will see the good in doing that and release more. look how much htc,samsung and others have gained releasing there source..The developers here like carliv,make their dev so much better and they know it. maybe mediatek will come around...
[Miscellaneous Android Development] lce67:
hey carliv..i was wondering if you would point me in the right direction with getting kernel to work with cyanogenmod? i cant believe it, but they let me download the source for my device...:D...I sent them a email and asked ...and i got a reply with directions on how to download it....wow...i couldnt belive it....

i followed there directions and it built out and worked...but looking at the source there are so many make files pointing to other make files..the directory tree is nothing like i have worked with before...

p.s your recovery is awsome on this phone it has saved me a few times now...:good:

was just going through files and noticed that it is the whole source to build AOSP......i was wondering why the zip file was 800MB...it even has boardconfig.....
[Miscellaneous Android Development] :
There is a thread for your question about release MTK to cyanogenmod, and at least two threads with alpha builds (I can't find the links now, but use search on xda). As you will find there, this is not an easy job. The Mediatek building tree is heavy customized, and you need a lot of patience and dedication to convert that for cyanogenmod. I can't give you any advice from personal experience because my laptop isn't good enough even to think of building kernels (about a whole ROM I didn't even thinked)... I hardly can make it build recovery, and I just upgraded the HDD to be able to use a bigger ccache to speed up the building process. When I will have enough money I will buy a proper computer for these tasks, but for now I have to use this.

In that thread you can read and ask advices from people who actually built kernels for mtk, and other stuff.

Cheers!
[Miscellaneous Android Development] eraycetin:
Can we port a recovery to a MTK Phone that doesnt have an external sd ? my phone only has internal storage and its a mtk phone?
[Miscellaneous Android Development] :
Sure, why not? You have to set the name for your sdcard as "/sdcard" not "/emmc" or "/internal_sd" in recovery.fstab.
[Miscellaneous Android Development] eraycetin:
Thanks for reply. So i have to edit all of the lines that has /emmc etc. > to /sdcard am i correct?
[Miscellaneous Android Development] :
No, only one in fstab and delete the other "/sdacrd"... But from your answer I guess you don't know much about these things. So, I will quote a part from my porting thread's OP:

And please, next time read more before asking questions, the answer might be already there. My time is limited and I don't like to repeat or write many times same answer.

Cheers!
[Miscellaneous Android Development] eraycetin:
Thanks! With your answer I discovered something else.

i allready have a recovery that made from flash tool but when i try to install zip from sdcard/internal it says "e:cant mount" error. so if just edit the line you said in fstab i can fix this error ?
[Miscellaneous Android Development] :
If you have only internal. aka one single sdcard, name it in fstab "sdcard" and in recovery menu chose install zip from sdcard, not internal. The recovery doesn't "know" if your sdcard is internal or external, you decide that, the recovery will threat "sdcard" as main storage and the other one, if exists, as secondary storage. To change this, in init.rc you have to change export EXTERNAL_STORAGE to what you want, but names are limited to "sdcard", "emmc" or "external_sd" in jellybean (CM-10.1) version.
[Miscellaneous Android Development] Swapnil Solanki:
I dont know what exact problem is.. All i know is that its giving some mount points errror. I used to fix it 5-6 times but then too it is giving that error. See that I've attached a image. I ported your recovery for my Android one device {sprout} . please help me [MENTION=5186178]carliv[/MENTION]
[Miscellaneous Android Development] :
Post here wrapped in CODE tags your recovery.fstab (the one you use in that recovery). I want to see what bad fstype do you have there.

Anyway in few days I will post a new porting guide along with my new versions, for porting - 2.7 for jellybean and 3.0 for kitkat. Maybe it will be easier to follow, because I will make a post about fstab.
[Miscellaneous Android Development] Swapnil Solanki:
Awesome :D
[Miscellaneous Android Development] Swapnil Solanki:
Fixed that but now 1 last bug remains i.e. Recovery reboots automatically sometimes any fix for it??
[Miscellaneous Android Development] Tech N You:
Master [MENTION=5186178]carliv[/MENTION] First of all great guide and congratulations for making this to PORTAL :good: :cool:

I need a guide to increase the OS partition in my device. I followed guide by Manish HERE but honestly it's a bit hard to cope up with please can you rewrite a Tutorial for this in a little simpler manner. I have this big request . Please consider it and help me. :)

Thank you :good:
[Miscellaneous Android Development] :
Ah, thanks. That is quite a surprise for me.

About increasing data partition guide, I don't have to write one because someone else already did it. It's the best guide for that from all I've seen. You can find it here. And another one here.
[Miscellaneous Android Development] Tech N You:
Thanks [MENTION=5186178]carliv[/MENTION] for quick reply. You misunderstood me, I meant SYSTEM partition where the ROM gets installed not DATA.
[Miscellaneous Android Development] :
The link you posted from M@nish was about increasing userdata (apps storage). I don't think you can increase system partition size in the same way. Even for userdata you need to have a phone with fat partition to work not data/media legacy. And it's possible because fat (internal sdcard) partition is the last one in scatter and if you alter it that doesn't have consequences on all the other partitions, but if you will alter system partition you need to change much more including some start adresses in scatter, which will make the scatter to not match with internal PMT from phone (in uboot) and you will get an error in SPFlashTools. To alter system partition you need the sources to build the firmware again with different partition table. Also I don't know why you need to increase system partition: the Android system won't take more than 1 Gb in any version you install, and if you need that for apps, then the link I gave to you is what you need, because apps are not installed in system, except for those included in the ROM.
[Miscellaneous Android Development] Tech N You:
Hmm I see. Thanks for the much needed clarification master [MENTION=5186178]carliv[/MENTION].

Let me explain why I am asking to increase system partition. As you said 1 GB is the maximum size for system partition, device Huawei Honor 3X G750 is running EMUI 3.0 and is having system partition around 1.04 GB.

I am porting this ROM to my device but unable to do it because it's system size is 1.04 and my device has 890 MB (which I know is enough to install any ROM) but problem is I can't deodex this RO, I tried various tools Universal deodexer, Ultimate Deodexer, Kamone Tool,Quick Script for deodexing etc but all in vain. I face some weird errors like "UNEXPECTED TOP LEVEL EXCEPTION blabla javaerror:175" plus one more wierd issue is framework file is 1kb and the odex is 10 MB.

So I am facing problems related to this. After removing all the bloatwares I get 903 MB system partition and that makes me really pissed off! I can't deodex any folder be it app, priv-app or framework folder. I also moved apps in data partition but then ROM shows weird things while booting up it shows boot animation then a black screen comes then again boot animation then again black screen. Tried everything won't work

So if you point me in the right direction I would be glad :)

thanx for all your help
[Miscellaneous Android Development] :
I assume you are working in windows from your post. That java issue is related to path I think: you need to use a newer jdk (not jre) and add java in your path - there are many guides about java path in windows here on xda or on stackoverflow. Also did you tried this tool? I didn't use it but it seems quite simple and if you update the smali and baksmali jars with latest ones it may work well. And a last thing, if the ROM has full gapps try to remove some of them or move them to user apps (let them to install from playstore later): youtube, maps, etc.
[Miscellaneous Android Development] Tech N You:
Yes I am using Windows. ROM has minimal gapps and Thanks for that quick tip! I'll update my jdk! I tried that tool too but had no luck but will try again after installing the updated jdk thanks :) :good:
[Miscellaneous Android Development] Hesham Sleem:
Great work...thank you Sir

It works good on Lenovo A3000
[Miscellaneous Android Development] breathstealer69:
Awesome guide...:):):)
[Miscellaneous Android Development] raviindia:
CTR for Karbonn smart A11 Star (MTK6572) Little problem

Dear Carliv,
[Miscellaneous Android Development] 8cpaiw:
Hi, I have TTEM A909 and it has MTK6592

It's soft bricked,I can enter TWRP

I did a full backup on CWM but I can't restore it using TWRP(not compactible)

So how to get back to CWM?

Can you link me the flashable zip?

When I try through CMD I get <Waiting for device>
[General Accessories] tipcell_company:
www.tipcell.com sell: audiovox 8910 housing, kyocera kx1 housing, kyocera kx1i housing, samsung a670 housing, LG vx6100 housing, audiovox 8600 housing, audiovox 8900 housing, LG 8000 housing, LG 4400/540 housing, LG 4500 housing, LG vx1 housing, samsung a530 housing, LG 6000 housing, samsung a310 housing, kyocera 2325 housing, kyocera se47 housing, LG vx3200 housing, motorola t720 housing, motorola v60s faceplate, motorola v120e housing, LG vx3100 housing, LG 1400 housing, LG 5400 housing, LG 8300 housing, kyocera se47 housing, kyocera 1155 housing, kyocera 1155 housing, LG 1300 housing.

mail: sales@tipcell.com

name: keiresing

MSN: keiresing9988@hotmail.com

http://www.tipcell.com

ICQ: 239470786
[AT&T LG G2] hcofamousgirl:
I haven't installed any roms on my phone its just rooted. Will I still get at&t's update for kit kat ?
[AT&T LG G2] LenAsh:
Even if you are offered the update, it will fail due to it being rooted. Some have reported semi-bricking also occurs.

Suggest you positively avoid any update unless or until you return to 100% Stock.
[AT&T LG G2] hcofamousgirl:
How can I unroot my device?
[AT&T LG G2] LenAsh:
Here

http://xdaforums.com/showthread.php?t=2432476
[AT&T LG G2] hcofamousgirl:
thanks a lot! I hope i don't screw anything = / have you done this before?
[AT&T LG G2] hcofamousgirl:
when i click the first link and go to at&t there are 3 options, which do i click to download?
[AT&T LG G2] tdevaughn:
Why do you want the ota? It will be leaked looking before att sends it out. Just install a Rom that incorporates the kit Kat release
[One (M7) Q&A, Help & Troubleshooting] AK!:
I've had this problem the moment I got it out of the box.. then for a week it stopped happening and then just happened again. It just turns off and no matter what buttons I press it's dead until I plug it in, then it starts charging and I turn it on and the battery is actually full so I unplug it and then it works fine. The phone is almost brand new, no root or custom ROM. Is there something I can do to prevent that from happening again?
[One (M7) Q&A, Help & Troubleshooting] alray:
yes, go back in store and ask for an other device. If shouldn't do that if everything is stock
[Google Chromecast] jerrygooch:
I have recently been unable to get any app to display on my TV. Most of the time I get audio but that's about it. I've tried hulu, YouTube, Google movies, and Google music with no luck. The home screen works fine though which is strange. Is there anyone who has had a similar issue?
[Google Chromecast] wptski:
I think you need to describe exactly what you are trying to use(Chrome on PC, Android , etc.) and what other apps alone or in combination. After that, I'm sure someone can help you.
[Google Chromecast] bhiga:
Please also tell us the manufacturer and model of your wireless router.
[G Pad 8.3 Q&A, Help & Troubleshooting] hasona:
So it came to my mind yesterday when I got a new Bamboo Stylus duo that the G pad digitizer recognizes input A LOT better than my Z1, nexus 7, hp laptop and countless other touch-enabled devices I have had before. Is there any info on why the capacitive digitizer is so good because it feels like other devices are good but not as good as the one inside the G Pad!.,
[Galaxy S III Q&A, Help & Troubleshooting] TDMaster:
Hello i want to install Firmware from Sammobile Firmwares.

Firmware: i9300XXUGMK7_I9300OJKGMK1_ILO

Odin Version : 1.95 , 3.07

Tried already :

Using odin on Windows 8.1 few computers and usb ports

using odin on Windows 7 few computers and usb ports

Windows version x86 and x64

different USB Cables.

Read all the forum Tutorials and Q&A.

any help would be great :)
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
Try another download first .

If you have read all the faqs and guides then you know you need a new motherboard .
[Sony Xperia Miro, Tipo (Dual), J, E] UltraGamerHD:
CyanogenMod 11 (Android 4.4.2) For Xperia E Project Home/Status Page​

Working:

Display

Audio

Bluetooth

WiFi

RIL

Video Playback (SW/HW)

Mobile Data (3G)

LED's

Magnetometer (Screen Rotate)

ART

Vibrator

Battery/Charging

Sound Recording

Not Working:

Camera

Video Recording

FM Radio

All Download Links at http://p.pw/bagB9E

Source: On My Github

Local Manifest: Click Here

Thanks To Everyone in the TamsuiCM11 Team Who Made This Possible!
[Sony Xperia Miro, Tipo (Dual), J, E] UltraGamerHD:
[MENTION=5067035]lozohcum[/MENTION]

Since I'm the only developer working on CM11 For Xperia E (Where is [MENTION=4534124]hsr0[/MENTION] ) I'm looking at where we can start at bug fixing. What information do I need to give you to diagnose the problems?.... I guess logcat etc.

This is what I did:

Compiled with using the lights.c from CM Repo

Compiled with all things under Audio commented due to AudioHardware.cpp Errors.

Compiled Using Default Toolchain.

SELinux is Still Disabled Although I have added the correct lines needed.

Where to go from now?
[Sony Xperia Miro, Tipo (Dual), J, E] NSDCars5:
Firstly, [MENTION=5395179]UltraGamerHD[/MENTION], can you please fix the thread title? It's says "4.2.2", where it should say "4.4.2". Awesome, thanks!

Secondly, whenever I try to sync, the local manifest causes problems. lozohcum said to download manually, but I'm not sure how to do that. I'm also doing CM11 - for now.
[Sony Xperia Miro, Tipo (Dual), J, E] UltraGamerHD:
Get a Fresh Install of Ubuntu 13.10 and Follow this guide here: http://xdaforums.com/showthread.php?t=2464683

Do Every Command EXCEPT FROM THE LAST 3

Now Type this in Terminal:

mkdir ~/cm11

cd ~/cm11

git config --global user.name YOUR NAME

git config --global user.email YOUR EMAIL

repo init -u git://github.com/CyanogenMod/android.git -b stable/cm-11.0

repo sync

---------------------------------------------------------------

Now lets setup the TamsuiCM11 Repo Manifest

Type this in Terminal:

. build/envsetup.sh

Then go into cm11 folder using the file manager and press Ctrl + H, you will now find a folder called .repo. Go inside the .repo folder.

Inside the folder create a folder called

local_manifests

Exit the folder back to the cm11 folder and press Ctrl + H again.

Now go back to Termial and Type:

gedit ~/cm11/.repo/local_manifests/local_manifest.xml

Copy this into the document:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<!-- Dependancies -->
<project path="device/sony/tamsui-common" name="TamsuiCM11/android_device_sony_tamsui-common" revision="cm-11.0" />
<project path="kernel/sony/msm7x27a" name="TamsuiCM11/android_kernel_sony_msm7x27a" revision="master" />
<project path="device/sony/qcom-common" name="CyanogenMod/android_device_sony_qcom-common" revision="cm-11.0"/>
<project path="device/sony/common" name="CyanogenMod/android_device_sony_common" revision="cm-11.0"/>
<project path="kernel/sony/nanhu_ds" name="TamsuiCM11/android_kernel_sony_msm7x27a-nanhu" revision="cm-11.0" />

<!-- Devices -->
<project path="device/sony/tapioca_ss" name="TamsuiCM11/android_device_sony_tapioca_ss" revision="cm-11.0"/>
<project path="device/sony/jlo" name="TamsuiCM11/android_device_sony_jlo" revision="cm-11.0" />
<project path="device/sony/mesona" name="TamsuiCM11/android_device_sony_mesona" revision="cm-11.0" />
<project path="device/sony/nanhu_ds" name="TamsuiCM11/android_device_sony_nanhu_ds" revision="cm-11.0" />
<project path="hardware/atheros/wlan" name="CyanogenMod/android_hardware_atheros_wlan" revision="jellybean" />

<!-- Proprietary files -->
<project path="vendor/sony" name="TamsuiCM11/proprietary_vendor_sony" revision="cm-11.0" />

<!-- Drivers -->
<project path="hardware/qcom/display-legacy" name="TamsuiCM11/android_hardware_qcom_display-legacy" revision="cm-11-jlo" />
<project path="hardware/qcom/audio-legacy" name="TamsuiCM11/android_hardware_qcom_audio-legacy" revision="cm-11.0" />
<project path="hardware/qcom/media-legacy" name="TamsuiCM11/android_hardware_qcom_media-legacy" revision="cm-11.0" />

</manifest>

Save and exit.

Then Type

repo sync

Your Done [MENTION=5129084]NSDCars5[/MENTION]
[Sony Xperia Miro, Tipo (Dual), J, E] lozohcum:
[MENTION=5129084]NSDCars5[/MENTION] go to github site of repo you want to use, let's say it's jlo in my case: https://github.com/TamsuiCM11/android_device_sony_jlo

Select brunch you want to use, and then click Download ZIP button on the right side.

Then upack that folder, rename to jlo and move to device/sony.

Same with other repos.

Btw after I redownlaod everything I don't have any problems with syncing.

You can work on Builduntu.

joebonrichie is working on CM11 too.

These days I can't give my time to CM11 because I'm doing driving license and have some school stuff unfinished. I also have matura exam in May.

At the moment I'm rebuilding rom due to problems with Audio HAL. [MENTION=5395179]UltraGamerHD[/MENTION] you have to find the most similar device to XE and see how other devs worked on it. Learn by observation, reading and trying, there os no single way to just fix errors. Many times reading logcat gives you the most important informations how to solve the problem, just think a lot an try to remember which file refers to what in logcat.

I'm not dev who can code, understand everything and can write app from scratch. But I've learned a lot first by porting roms and then by

reading the code for tens of hours.
[Sony Xperia Miro, Tipo (Dual), J, E] NSDCars5:
[MENTION=5067035]lozohcum[/MENTION], [MENTION=5395179]UltraGamerHD[/MENTION]: Thanks a lot! I'll try these soon as I get home. Buildbuntu in particular looks pretty awesome.

For some related development, I say we should look at the HTC Explorer and the LG Optimus L7; both are pretty similar to the E, hardware-wise (well, we also have the Galaxy Ace Plus, but I think lozohcum said we shouldn't look at Samsung for development).
[Sony Xperia Miro, Tipo (Dual), J, E] UltraGamerHD:
Thanks for the Advice.
[Sony Xperia Miro, Tipo (Dual), J, E] lozohcum:
Just be carefull with samsung. Source porting is fine that way.
[Sony Xperia Miro, Tipo (Dual), J, E] joebonrichie:
[MENTION=5395179]UltraGamerHD[/MENTION]

I've noticed some differences between FXP CM11 tamsui-common-legacy (jlo/tapioca/mesona) and tamsui-common (nanhu).

in tamsui.mk, tamsui-common-legacy has the following snippet for RIL

# Radio
PRODUCT_PROPERTY_OVERRIDES += \
[B]ro.telephony.ril_class=SonyQualcommRIL7x27a \[/B]
[B]ro.telephony.ril.v3=skipnullaid \[/B]
rild.libpath=/system/lib/libril-qc-1.so \
rild.libargs=-d/dev/smd0 \
persist.rild.nitz_plmn= \
persist.rild.nitz_long_ons_0= \
persist.rild.nitz_long_ons_1= \
persist.rild.nitz_long_ons_2= \
persist.rild.nitz_long_ons_3= \
persist.rild.nitz_short_ons_0= \
persist.rild.nitz_short_ons_1= \
persist.rild.nitz_short_ons_2= \
persist.rild.nitz_short_ons_3= \
ril.subscription.types=NV,RUIM \
DEVICE_PROVISIONED=1 \
keyguard.no_require_sim=1 \
ro.ril.hsxpa=1 \
ro.ril.gprsclass=10 \
ro.use_data_netmgrd=true \
persist.data_netmgrd_nint=3 \
ro.ril.transmitpower=true

in tamsui.mk, in tamsui-common (nanhu)

# Radio
PRODUCT_PROPERTY_OVERRIDES += \
[B]ro.telephony.ril_class=SonyQualcommRIL \[/B]
[B]ro.telephony.ril.v3=qcomdsds \[/B]
ro.telephony.call_ring.multiple=false \
rild.libpath=/system/lib/libril-qc-1.so \
rild.libargs=-d/dev/smd0 \
ril.subscription.types=NV,RUIM \
DEVICE_PROVISIONED=1 \
keyguard.no_require_sim=1 \
ro.use_data_netmgrd=true \
ro.ril.transmitpower=true \
persist.data.ds_fmc_app.mode=0 \
persist.ims.regmanager.mode=0

i've bolded the importance differences between the two, as you can see nanhu used a different RIL. If we can find SonyQualcommonRIL.java about somewhere maybe we could fix RIL on nanhu.
[Sony Xperia Miro, Tipo (Dual), J, E] NSDCars5:
So I found this SonyQualcommRIL.java; see if it can be used: https://github.com/OpenSEMC/android...telephony/java/com/android/internal/telephony
[Sony Xperia Miro, Tipo (Dual), J, E] UltraGamerHD:
[MENTION=5428039]joebonrichie[/MENTION]

It's been found