Search results

I decompiled the APK, this is the android manifest of the GBA app from mediatek: <?xml version="1.0" encoding="utf-8" standalone="no"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" android:sharedUserId="android.uid.phone" package="com.mediatek.gba"...

The BLU can't power any usb key or any other kind of device it's micro-usb port. You need to use a OTG cable connected to a powered source to make the BLU see anything. You can find online some Y OTG Cable made for this, to power the external device.

By following the advice of superdragonpt, you should check this devices tree: https://github.com/MediatekAndroidDevelopers/android_kernel_jiayu_s3plus_n560a https://github.com/MediatekAndroidDevelopers/android_device_jiayu_s3plus_n560a and last...

Removed

Moved

You can see here a tutorial on how to build for MTK. the post does provide some patches to be applied on the Android Tree. I doubt those patches are up-to-date with anything else than android 5 or even 4.4 http://forum.xda-developers.com/showthread.php?t=2754145

By googling a little and asking some help to other MTK dev, I found this: https://github.com/mtker/MT6735_Longcheer This is not for our device, but it's a full setup for another device with the same chipset. Now I have no idea if it's android 6 or 5

The fingerprint is: BLU/full_p6601/p6601:6.0/MRA58K/1467008010:user/release-keys You should be able to buy it off eBay. Amazon.com doesn't even ship it to Canada ... it's a US exclusive for now. (Got mine through eBay)

I confirm that I kept the encryption and I had no issue whatsoever with the change Prime -> OEM.

I'll give it a try then :) Thanks. I must have misread then, maybe that should be clearly said in the first post that keeping root + twrp = no more OTA. If I understood correctly, unrooting the device, rebooting, and the BLU recovery is back, right ?

Hello ColtonDRG, Two questions for you : 1. Can I change from Prime to non-Prime when the device is already encrypted ? 2. Are you sure that putting TWRP is not blocking the OTA ? The OTA need the BLU recovery to apply, without it, I don't think TWRP is able to apply the OTA updates.

A basic AOSP, no fancy feature, no cyanogen. Just the ROM without any bull****. That would be perfect to after start modding, and see what we can really do with the phone. Something like Kresus

It's an excellent ROM, the most stable 6.0 I tried for my old Nexus. Thanks again for porting it! I'm using it with an ext4 system partition, F2FS cache, and F2FS data. It works flawlessly and without lag, it's really amazing compared to the other roms I tried in the past.

I confirm it works great with Dirty Unicorn 9.1 I would enjoy having zram on the kernel.

Sorry I mislead you. There is a solution, we need to reactivate the system update service to remove the wake lock. It has been corrected in the version of CM after the 29 June. Source : http://forum.cyanogenmod.com/topic/96459-systemupdateservice-wakelock-on-cm11-m7-massive-battery-drain/ It...

Deleted. Wrong information.

Well that's how the FS is after a clean install. If you check the install script, it does format the system partition before putting any file onto it. For an unknown reason after the first boot, the partition get filled. Edit : Okay, I found the reason : Slim_AIO_gapps. Don't install the full...

Yup : That what the df command is telling me. I think it's quite weird, because if I do a du -s /system I get : 1048576 system There is something wrong with filesystem for the /system partition because I have no problem for the cache or the data partition that are giving the correct size.

Wonderful rom. I just have one problem with it. I can't add new file into the system partition, it always tell me there is no space left (when there is 15 Mo minimum left). When I wanted to installer Viper4Android I had to hack the ROM installer to add directly into it the file needed for the...

Thanks for that answer (and sorry for my late thanks). As a Tipo (Single) User I think I'll stay with the Stock kernel, since there seems to have issues with the Vengeance one. I would like also to report a bug. The notification led doesn't work for me. (I tried with Hancent with the test...

Well that I understood, and it seems that only Vengeance is based on it. But for what I read, it doesn't seems to work with the device (and the dev of Gimlo even asked to return to stock kernel before flashing Gimlo). That's why I'm asking.

I'm using the rom and I'm quite happy with it. I just wanted to know which kernel I can flash with it ? I wanted to try the Riches one but if I'm right it's only for CM10 (JB).

With the today update I have exactly what is describe in this image : Is there a way to get back the normal battery percentage ? Edit : I installed the last CM nightly now, and the bug is not present, It must be one of the commit you cherry-picked.

Installation problem Hey Well here is what happened to me : efs erased Gapps without play store Hopefully I had the backup in /sdcard/backup/efs but it took me time to find where I needed to restore it, since I had no /efs folder mounted or anything else that could have lead me to that. I...

I'm using the stock UI, 180 ppi and without any nav bar (replaced by the Pie) but I kept the status bar. Like that it's really wonderful, you have easy access to everything, and you get back some place on your screen !

That's how I understand it. Since the idea of the "Persistent notification" is to "shame the developer" that use in an improper way the foreground process. The way it works shouldn't change.

zuhang There is clearly a Killing App problem with Android 4.3, and that's because they changed how the Foreground service is working. Source : https://plus.google.com/105051985738280261832/posts/MTinJWdNL8t It seems for now, there is now way to have an application that stay in memory, Android...

I have the exact same problem as flvinny521 . On any 4.3 ROM I tried so far, it seems that for any real reason the application get killed and restart. Since I'm using a bluetooth headset it's quite annoying, I have to stop and restart the headset for Viper to detect is as bluetooth and not stay...

Could you ask DariosF to put a link in the OP pointing directly to one of your post with some kind of Big Changelog and update ? It will be easier to keep track of your improvements, since you clearly update the kernel more often than the ROM :)

Thanks for the release. I went from SentinelRom to SmoothRom and now yours. For now I have the smoothest experience with Purity :) I'm going to test it intensively :)

It's maybe because I reset the phone (I messed a little with the store.vol and PimIndex.vol because I wanted my sms back (without any success ... duplicate contact, etc ...)). I didn't check if before the reset I had the Nokia Collection.

I installed it today without any problem. Just had a little bug with the Market, I couldn't find the Nokia Collection ... I used winTT to put it back and since the restart, no problem at all :) Thanks for your work :D Only little thing ... I'm not quite a fan of the new smileys, is there a cab...

By default NSS is saving the Nokia DLOAD when you are replacing it by the QLOAD. You have a restore button that make you go back. Never tried, but should work. (Since it doing exactly the same operation (rewrite the bootloader) with another one). Don't forget it's ONLY for Nokia Lumia 710. As...

This one is perfect : http://forum.xda-developers.com/showthread.php?t=1721355 Only follow the A part, for the B part use this tool (Lumia Downloader)

Hi, I downloaded NSS, NCS, installed driver and want to flash the Qualcomm BootLoader. Then I followed the instruction, launch my device in OSBL and put it in the computer. The phone is detected as Nokia USB Connectivity and in OSBL mode by NSS but I don't have any "Windows want to format"...

If I'm right, this one is the real dev of the application and come here with his new version :)

I don't see how I can improve it. I mean the CWM bug with ext4 should be only corrected if I look the code (or take a newer version) and add it to the kernel. Problem is, I found the code on github, but no instruction on how to compile it .... And for backporting 3.0 Kernel to our device, we...

disable zCache and zRam.

try wipe Dalvik cache and the cache partition. In the custom install what did you choose ?

Try using the Xperia theme or the ICS. (but I'm sure the Xperia is working fine) I still search what can cause that ... since it's a port of the 5.0 there is some incompatibilities

I have done an updated version with Auto-brightness and the new brightness slider. I upload it, since we have no news of SMOK Edit : Link : http://yadisk.cc/d/ghGWTRhuopi Changes :

If my memory is right it's just impossible because Android doesn't support natively that feature of Bluetooth. If you want it, you have to first add the support for it in Android ... good luck.

I prefer to use lbe security :) It's not needing any patch, just to be rooted and doing exactly the same Sent from my GT-I9000 using xda app-developers app

About Quadrant, you must know that this score doesn't mean anything in term of comfort, feel of speed, or anything an user can "feel" about the rom. Moreover, Quadrant is giving too much point for the I/O, there are some articles here on XDA that are speaking about that. Trying to put the...

Where can I find lidroid panel ? For GPS, the lib is incorrect but working, just not giving the right number of satellite.

ICS design. /system/lib/hw of 4.0 : http://www.mediafire.com/?7q8slherwnba8c8 You'll see that only the file gps.s5pc110.so is different (33,8 Kb) About haptic feedback. When you are using one of the capacitor button, the device should be vibrating. Edit : for the Auto brightness I used that...

I'm interested yes :) This feature is quite useful when going out/in . By the way I discover that the GPS lib (/system/lib/hw) is not the same on this ROM as in the stock 4.0 one. The gps is working ... in a strange way, it's telling me he have 2 satellites ... with one of a SNR of 200 ...

Can you add the Haptic feedback in the settings as in the normal one ? And also the possibility to set the Brightness to automatic :) Thanks for your great work

It what I thought too ... then I used my own compilation of busybox, and used it to mount manually (like in the init.rc) the filesystem. I had still the bug ... You can check by yourself : 1) Launch the recovery 2) wait some second for adb to launch 3) adb shell 4) busybox | head 5) You'll see...

You can have it using More Locale 2 if you don't want to wait :D Thanks for you Work Smok :D It's really fast OO the fastest rom I ever had :)