Database Develop

Replacing libraries to record calls with total-recall

Hi,
I was looking at killer mobile website -
http://www.killermobile.com/applications/android/total-recall-android-|-call-recorder.html
and I saw that under the section of -
"Confirmed on the following Android Devices (No Rooting Required)"
the galaxy i9000 will work with their call recording app if it's running android 2.2.1.
Further at the bottom, there is another section -
"Requires Custom ROM/Kernel/Libs w/Rooted Device"
and there it says that the application will work with the i9000 if libraries are replaced, and there is a link for those libraries to download.
If I'm running 2.3.6 (JW1), and will replace those libraries, will the app be able to record calls on my device?

Custom Bluetooth module for Nexus 5 (4.4.3) that works with BMW's ULF car kit

Apologies for the links: as I am a new user, I am not allowed to directly link to outside sources. Please replace _ with :// or . (Forum suggestion: use optional pre-publication review for posts from new users that depend strongly on external links.)
INTRODUCTION: My BMW 318 (E46, 2004) had a factory default BMW ULF bluetooth module (early generation) that worked fine with my BB Q10 and all phones up to Android 4.1. From 4.2 onwards, I and many others have been having problems with keeping the Bluetooth connection alive for more than a few seconds. This has been widely reported but never addressed in stock Android. As even the latest OTA upgrade to 4.4.3 didn't solve it, I decided to compile the required Bluetooth kernel module myself.
BACKGROUND: The change from the Bluez to Bluedroid system in Android 4.2 caused the compatibility issues. User 'wulu' at the forums of CyanogenMod reported on how he patched his CM10.2 (and later) to include a patch that solves the issue. I repeated his procedure for stock 4.4.3 for the Nexus 5.
Markus Schmidt's problem description & patch: https_github_com/Root-Box/external_bluetooth_bluedroid/commit/97d2f6346bad56299f60cfcd8c45ad893a0da78c
Wulu's specifics for Nexus 5 & BMW's ULF for CM: http_forum_cyanogenmod_com/topic/77834-bluetooth-connection-drops-car-kit-bmw/
METHODS:
The following procedure is specifically to compiled the Bluetooth kernel module for the Nexus 5 hardware and the 4.4.3_r1.1 (OTA) release. It should therefore only work for this specific combination. If you want to compile the module yourself, please read the linked pages with Google's excellent instructions: http_source_android_com/source/initializing.html
Here are a couple of notes I made that deal with some specifics for my Mac and the Nexus 5:
On Mountain Lion (Mac), I had to use Xcode 5.0.2 to get past a compile error. See instructions here on how to download and use the older 5.0.2 version of Xcode: https_groups_google_com/forum/#!topic/android-building/FPCSo1xKJ4U
Do not download the "master" source using the repo command, but download "android-4.4.3_r1.1". The master source has post-OTA changes that make a compiled module incompatible with the OTA release for the Nexus 5. "android-4.4.3_r1.1" was listed on those pages as specifically the version that was used for the OTA 4.4.3 upgrade for the Nexus 5.
Setup the environment as instructed and add the three proprietary driver sets listed for the Nexus 5 and 4.4.3 (see "Building for devices" on the Google pages).
There is no need to use the full patch. You can make the two small modifications to the bta_ag_sdp.c file using any text editor. Find the file first (find . -name "bta_ag_sdp.c") and commend out the two lines with the minus signs given in wulu's the first post (or Markus Schmidt's patch) by putting a # in front of both lines: #if (p_scb->peer_features == 0), #p_scb->peer_features = p_attr->attr_value.v.u16;.
Select the "aosp_hammerhead-userdebug" (=Nexus 5) option with the lunch command, and compile using the make command. I was able to follow the instructions pretty much to the letter without any problems.
After the compilation I had two version of the file, in four locations. They are easily found using the find command (find . -name "bluetooth.default.so" -exec ls -la {} \. The bigger one (in the symbols subdirectory) is for debugging. The smaller one is the one I used (and which is linked in this message). It was located at "./out/target/product/hammerhead/system/lib/hw/bluetooth.default.so" in my source tree.
After this, it was pretty straightforward. I rooted my Nexus 5, re-installed FX (with paid-for Root add-on, but the free ES File Explorer should also work), uploaded the file via Dropbox and its Save to SD, transferred it to the R/W mounted system directory to replace /system/lib/hw/bluetooth.default.so with it, and restarted my phone. I also modified the config file (/system/etc/bluetooth/auto_pair_devlist.conf) that blacklists BMW components by commenting out most lines, but I am not sure if this is helpful or not.
RESULTS: It seems a little bit less stable than the Bluetooth connection I had with my Blackberry, but it definitely works. I was able to transfer my contacts and to make and receive calls. For anybody with stock KitKat 4.4.3 on the Nexus 5, here is the bluetooth.default.so kernel module: http_s000_tinyupload_com/index.php?file_id=07750725920558658087
DISCUSSION: The compilation procedure can undoubtedly be optimized. I compiled the entire source tree over several hours, just to be sure I didn't miss out on things. Feel free to give tips, but I'm happy that it worked at all.
CONCLUSION: Thanks to wulu's advice in the CM forum thread I was able to compile a patched Bluetooth module for stock Android with KitKat 4.4.3 that works with my BMW 318 (E46, 2004) ULF car kit.

That´s great! :good:
Is it possible for you to provide the same for Nexus 5 - 4.4.4 OTA ?

mnasty said:
That´s great! :good:
Is it possible for you to provide the same for Nexus 5 - 4.4.4 OTA ?
Click to expand...
Click to collapse
Yes, great job!
Nobody have already done this for 4.4.4 ? I'll do this if I have time.

ZeroKcm said:
Yes, great job!
Nobody have already done this for 4.4.4 ? I'll do this if I have time.
Click to expand...
Click to collapse
4.4.4 from 4.4.3 is only security fixes, everything else is the same.

Does 5.0 Lollipop resolve the BMW ULF connection issue?
guys, do you think 5.0 Lollipop would resolve the current BMW ULF connection problem? Have anyone tried the 5.0 yet ?
I'm still in 4.4.3 working great on N5 paring ULF 8th Gen kit, thanks for S1010, wulu and Alpejohn guiding me the entire process.

REV HRD said:
guys, do you think 5.0 Lollipop would resolve the current BMW ULF connection problem? Have anyone tried the 5.0 yet ?
I'm still in 4.4.3 working great on N5 paring ULF 8th Gen kit, thanks for S1010, wulu and Alpejohn guiding me the entire process.
Click to expand...
Click to collapse
I have the same disconnect issue with my Seat, haven't tried the fix cause I was running 4.4.4 and there was no ready module for it, but lollipop didn't fixed it. I tried compilation without success. I followed all the instructions and compiled it successfully, but after replacing it, bluetooth fails to start. In the logcat logs I can see that it complains there is no bluetooth (something like that, don't have the exact logs to check it now), seems the compiled so file is not compatible.
If anyone can give a hand on this

Not sure if Seat using the same implementation as BMW ULF kit provides, my family also has a 06 Audi A4 with stock BT, I don't experience any connection issue from the stock 4.4.3 on N5. I would think Audi / Seat might use the same BT module as they share most of the VW parts.

I experience the same disconnects. I was experiencing it and with the old phone Galaxy Nexus, till one day I updated to cyanogenmod and the problem was gone. Then changed the phone with Nexus5 and again I have the same issues, tried everything with no luck. Changing the kernel, doing some stuff with paid bluetooth apps to manage the phonebook that the car is accessing. So I suspect the problem is the same
(Seems I'm still not able to post links, I just prepared one with the Blutooth device model number and year on it, if it mean anything to someone it is from 03.2007).

Don't work in lollipop, in your free time please compile a new file.
Thks.
S1010 said:
Apologies for the links: as I am a new user, I am not allowed to directly link to outside sources. Please replace _ with :// or . (Forum suggestion: use optional pre-publication review for posts from new users that depend strongly on external links.)
INTRODUCTION: My BMW 318 (E46, 2004) had a factory default BMW ULF bluetooth module (early generation) that worked fine with my BB Q10 and all phones up to Android 4.1. From 4.2 onwards, I and many others have been having problems with keeping the Bluetooth connection alive for more than a few seconds. This has been widely reported but never addressed in stock Android. As even the latest OTA upgrade to 4.4.3 didn't solve it, I decided to compile the required Bluetooth kernel module myself.
BACKGROUND: The change from the Bluez to Bluedroid system in Android 4.2 caused the compatibility issues. User 'wulu' at the forums of CyanogenMod reported on how he patched his CM10.2 (and later) to include a patch that solves the issue. I repeated his procedure for stock 4.4.3 for the Nexus 5.
Markus Schmidt's problem description & patch: https_github_com/Root-Box/external_bluetooth_bluedroid/commit/97d2f6346bad56299f60cfcd8c45ad893a0da78c
Wulu's specifics for Nexus 5 & BMW's ULF for CM: http_forum_cyanogenmod_com/topic/77834-bluetooth-connection-drops-car-kit-bmw/
METHODS:
The following procedure is specifically to compiled the Bluetooth kernel module for the Nexus 5 hardware and the 4.4.3_r1.1 (OTA) release. It should therefore only work for this specific combination. If you want to compile the module yourself, please read the linked pages with Google's excellent instructions: http_source_android_com/source/initializing.html
Here are a couple of notes I made that deal with some specifics for my Mac and the Nexus 5:
On Mountain Lion (Mac), I had to use Xcode 5.0.2 to get past a compile error. See instructions here on how to download and use the older 5.0.2 version of Xcode: https_groups_google_com/forum/#!topic/android-building/FPCSo1xKJ4U
Do not download the "master" source using the repo command, but download "android-4.4.3_r1.1". The master source has post-OTA changes that make a compiled module incompatible with the OTA release for the Nexus 5. "android-4.4.3_r1.1" was listed on those pages as specifically the version that was used for the OTA 4.4.3 upgrade for the Nexus 5.
Setup the environment as instructed and add the three proprietary driver sets listed for the Nexus 5 and 4.4.3 (see "Building for devices" on the Google pages).
There is no need to use the full patch. You can make the two small modifications to the bta_ag_sdp.c file using any text editor. Find the file first (find . -name "bta_ag_sdp.c") and commend out the two lines with the minus signs given in wulu's the first post (or Markus Schmidt's patch) by putting a # in front of both lines: #if (p_scb->peer_features == 0), #p_scb->peer_features = p_attr->attr_value.v.u16;.
Select the "aosp_hammerhead-userdebug" (=Nexus 5) option with the lunch command, and compile using the make command. I was able to follow the instructions pretty much to the letter without any problems.
After the compilation I had two version of the file, in four locations. They are easily found using the find command (find . -name "bluetooth.default.so" -exec ls -la {} \. The bigger one (in the symbols subdirectory) is for debugging. The smaller one is the one I used (and which is linked in this message). It was located at "./out/target/product/hammerhead/system/lib/hw/bluetooth.default.so" in my source tree.
After this, it was pretty straightforward. I rooted my Nexus 5, re-installed FX (with paid-for Root add-on, but the free ES File Explorer should also work), uploaded the file via Dropbox and its Save to SD, transferred it to the R/W mounted system directory to replace /system/lib/hw/bluetooth.default.so with it, and restarted my phone. I also modified the config file (/system/etc/bluetooth/auto_pair_devlist.conf) that blacklists BMW components by commenting out most lines, but I am not sure if this is helpful or not.
RESULTS: It seems a little bit less stable than the Bluetooth connection I had with my Blackberry, but it definitely works. I was able to transfer my contacts and to make and receive calls. For anybody with stock KitKat 4.4.3 on the Nexus 5, here is the bluetooth.default.so kernel module: http_s000_tinyupload_com/index.php?file_id=07750725920558658087
DISCUSSION: The compilation procedure can undoubtedly be optimized. I compiled the entire source tree over several hours, just to be sure I didn't miss out on things. Feel free to give tips, but I'm happy that it worked at all.
CONCLUSION: Thanks to wulu's advice in the CM forum thread I was able to compile a patched Bluetooth module for stock Android with KitKat 4.4.3 that works with my BMW 318 (E46, 2004) ULF car kit.
Click to expand...
Click to collapse

FYI, had similar issue with 2009 E61 5 series. Solution was third party app (Bluetooth Phone book) and a full software update for the car from the dealer. The app cost a few quid, the dealer software update much more!
That said, it works perfectly with stock Lollipop and I consider it money well spent.
---------- Post added at 09:15 PM ---------- Previous post was at 09:13 PM ----------
FYI, it was this app: https://play.google.com/store/apps/details?id=com.android_rsap.irmc

[Q] Help for a Newbie in P7

Hello ,
I got my P7 for about 4 Months now,
and I wanted to have the EMUI 3.0 and Lolipop
but I think the Original System is 4.4.2 and Emui 2
I want to ask What can I do to Root or make a ROM (Sorry I really dont know he defrance total newbie ) , but I dont want to lose the support of Google or the Google Market , what should I do , can anyone help me in that ???
give me details and tell me what to do
thanks

look at this: http://forum.xda-developers.com/asc...7en-rom-v3-0-emui-3-0-4-4-2-18-11-14-t2945104

darkzero2022 said:
Hello ,
I got my P7 for about 4 Months now,
and I wanted to have the EMUI 3.0 and Lolipop
but I think the Original System is 4.4.2 and Emui 2
I want to ask What can I do to Root or make a ROM (Sorry I really dont know he defrance total newbie ) , but I dont want to lose the support of Google or the Google Market , what should I do , can anyone help me in that ???
give me details and tell me what to do
thanks
Click to expand...
Click to collapse
If you are newbie than do nothing ! Wait for official upgrade ! Because you will cry !
Sent from my HUAWEI P7-L10

Ziolek67 said:
If you are newbie than do nothing ! Wait for official upgrade ! Because you will cry !
Sent from my HUAWEI P7-L10
Click to expand...
Click to collapse
Really ???? Why ?? Huawei is too slow in making the Updates , all now is Andoird 5 and P7 is stuck in 4.4.2

It's proberly better staying on 4.4.2 than on lolipop. Many bugs on lolipop.
Sent from my HUAWEI P7-L10 using XDA Free mobile app

darkzero2022 said:
Really ???? Why ?? Huawei is too slow in making the Updates , all now is Andoird 5 and P7 is stuck in 4.4.2
Click to expand...
Click to collapse
Ok than lest go to update.... I will waiting for yours requests for help

darkzero2022 said:
Really ???? Why ?? Huawei is too slow in making the Updates , all now is Andoird 5 and P7 is stuck in 4.4.2
Click to expand...
Click to collapse
Wow do you realize android 5 has been out officially for a week or two and pretty much every phone apart from nexus which uses the software directly from Google themselves who make android, still don't run it yet and expect to be running it in 2015.
Not even big teams that use the aosp code directly such as cyanogen or paranoid have got a stable fully functional rom out yet.
It takes time for the 3rd party developers to customize and test android for there devices once the official version gets released as they all use the final source code which only has been out 3-4 weeks.
Also no company apart from Google is much better, Samsung are still rolling out 4.4 to some of there devices with some like the s2 still on 4.2 and end of life presumably others will jump straight to lollipop from 4.3 etc.
Also on rooting what do you wish to achieve by doing so?
Rooting can be very dangerous if you don't know what your doing with devices like ours.
Take a look for example at all the posts in this forum asking to downgrade their l10's from emui 3 to 2 which they upgraded to custom versions etc without thinking and the issues they now have with boot loops and stuff.
If you want to run xposed you can find many people with similar things recently in this forum that can't get it to work.
Also rooting etc you lose the ability for any future updates via OTA and recovery and would need to manually update your device potentially bricking it every single time which bricking means you can no longer use your device and have to buy a new one.
Also are you capible on the PC with using it, command prompt Linux shell etc and doing things like installing Windows and other things.
If not then rooting is not for you.
Also do you know how to code in Linux C etc and know the workings of the Linux os, if not then there is no way you are going to make a custom rom. All you might be able to achieve is just repackaging someone else's ROM with minor edits and even then the tools to do that mainly use Linux to run as it's native windows doesn't have all the stuff Linux has natively in this regard.

Ziolek67 said:
If you are newbie than do nothing ! Wait for official upgrade ! Because you will cry !
Sent from my HUAWEI P7-L10
Click to expand...
Click to collapse
drguild said:
Wow do you realize android 5 has been out officially for a week or two and pretty much every phone apart from nexus which uses the software directly from Google themselves who make android, still don't run it yet and expect to be running it in 2015.
Not even big teams that use the aosp code directly such as cyanogen or paranoid have got a stable fully functional rom out yet.
It takes time for the 3rd party developers to customize and test android for there devices once the official version gets released as they all use the final source code which only has been out 3-4 weeks.
Also no company apart from Google is much better, Samsung are still rolling out 4.4 to some of there devices with some like the s2 still on 4.2 and end of life presumably others will jump straight to lollipop from 4.3 etc.
Also on rooting what do you wish to achieve by doing so?
Rooting can be very dangerous if you don't know what your doing with devices like ours.
Take a look for example at all the posts in this forum asking to downgrade their l10's from emui 3 to 2 which they upgraded to custom versions etc without thinking and the issues they now have with boot loops and stuff.
If you want to run xposed you can find many people with similar things recently in this forum that can't get it to work.
Also rooting etc you lose the ability for any future updates via OTA and recovery and would need to manually update your device potentially bricking it every single time which bricking means you can no longer use your device and have to buy a new one.
Also are you capible on the PC with using it, command prompt Linux shell etc and doing things like installing Windows and other things.
If not then rooting is not for you.
Also do you know how to code in Linux C etc and know the workings of the Linux os, if not then there is no way you are going to make a custom rom. All you might be able to achieve is just repackaging someone else's ROM with minor edits and even then the tools to do that mainly use Linux to run as it's native windows doesn't have all the stuff Linux has natively in this regard.
Click to expand...
Click to collapse
Thanks For your Valuable words,
I really enjoyed them and get my mind open
well I do have Good Experience in linux and Command line , C Programming actually didnt go deep with it really ,
But i think I will stick to your opinion and wait ,and while I do so I will learn more about the whole subject ,and maybe increase my knowledge in this Field . (Android Programming - the C Programming - how things work in Android , ROMS , ETC)
but would you mind telling me from where to start ???

darkzero2022 said:
Thanks For your Valuable words,
I really enjoyed them and get my mind open
well I do have Good Experience in linux and Command line , C Programming actually didnt go deep with it really ,
But i think I will stick to your opinion and wait ,and while I do so I will learn more about the whole subject ,and maybe increase my knowledge in this Field . (Android Programming - the C Programming - how things work in Android , ROMS , ETC)
but would you mind telling me from where to start ???
Click to expand...
Click to collapse
Apologies if I came across about abit hard this forum has had allot of impatient people jumping in recently trying to run Emui 3 on l10's then asking to downgrade as you may have noticed the other teams like paranoid are already dealing with lots of people saying there to slow for not having lollipop out within a hour of aosp.
I had the same issue running a custom Minecraft server that people got really angry then refused to play and bad mouth the server if we didn't update that day when update time for us was about a week given the number of customizations we had 41 plugin's in the end, sometimes longer if there were more changes the mod and custom server devs had to deal with.
Emui 3 and lollipop has more bugs more as it's new from what I found I may start a proper consolidated emui talk thread later for those running it opposed to all the l10 when are we getting it out help me downgrade threads.
The place I think you should start is to download the source code for your version from the emui webpage and start analyzing it out of interest.
There's another Dev on here doing the same thing so you might want to contact him for info.
Also there are tools on Linux that easily let you unpack stock image files and the ext container and repack them.
That way you can see the full file structure and how a rom is packaged.
It's good just to see what's inside roms and how the first roms are usually made by a repackage before source.
I will stress the same as above that while these are starting points you would need to know what you are doing and something more hackable like a cheap nexus or or Chinese tab (about $50 USD) with easy upgradable firmware something would be better to start on.
Also grab down the android tools with eclypse for Linux, the sdk virtual device and have a play around making a app and stuff also you can edit the virtual rom safely etc.
The Linux version of the tools is far superior as you can natively mount the virtual ext cards for host file transfer and do other things which you can't under windows.
By ext above I mean the virtual partition files which are either ext 3 or 4 last time I looked.
I'm not a coder myself and I only did basic stuff in the past as I had a Chinese android 2.2 tablet the MID ones as my first device, I used a custom rom on which was just a repack with file system changes with bloat removed etc.
I looked into this out of interest and curiosity, each rom update I repacked it with the apps I used so I didn't need to reinstall them, there was probably a better (proper) way than just unpacking the ext file system from the img adding my apps in to the deploy folder and repacking.
Also I unpacked a APK weather app etc to make changes and use a custom background and others like themes to grab icons and assets this is a good start with looking at app packages and how that all works as well as making your own app in various tools eclipse for one which is the official tool but there's hundreds of android programming softwares online even to do simple stuff as make a stand alone html5 app from a webpage.
The tools on Windows I found were lacking and harder to find for the rom stuff, with Linux it was built into the system a lot of things.
What Linux is the best for doing Android stuff I don't know so that will need to be researched.
As mentioned devices can be dangerous for custom stuff especially newer ones with bootloader security, the older Chinese style ones and some others you could reflash easily from sdcard with a update.img file as they didn't contain that lock out security on boot and debugging.
I nearly bricked a few devices in the past, once having to rely on the bootloader and Android Commander a powerful tool and device terminal to mount the partition rw while in the bootloader to rename a file backI renamed as a test that caused the system to stop booting.
You can still get some tabs that do that about 50 USD on eBay etc I think.

darkzero2022 said:
Hello ,
I got my P7 for about 4 Months now,
and I wanted to have the EMUI 3.0 and Lolipop
but I think the Original System is 4.4.2 and Emui 2
I want to ask What can I do to Root or make a ROM...
Click to expand...
Click to collapse
I'd strongly advise that you wait. My experience. You can root v4.4.2 VERY easily using vroot. Wait for lollipop, honestly. Is a nightmare recovering your position if you try to move now.
Sent from my HUAWEI P7-L10 using XDA Premium HD app

[PLEASE HELP] Lenovo K3 Note (K50-T5)

Hello to all guys , I just got this fantastic Lenovo phablet , but I do not like the translation and Vibe UI , I want to find a pure Android rom . I know that almost certainly there are devices that have the Lenovo compatible roms . Can anyone help me out ? :crying::crying::crying:

I have the same problem, I just changed to new version of VibeUI and had some problems with google apps HELP!

I'm pretty sure as this phone is, new rooting and roms are still being developed. Be patience.. or learn to make one yourself
To those who find this thread do be careful! I've already seen posts about people who have bricked this phone trying to root it.

Got the same phone. Liking the layout etc. Not the official VIBE UI rom.
It's set to English, but still finding Chinese icons/text everywhere.
Since I don't speak/read Chinese; issue...
Also sometimes laggy, due to lots of processes/apps running in the background, which can not be deleted or stopped.
Looking forward to when the community embraces this phone, and stock Android ROMS will be available on short term.
It's a (edit: potential!) flag-ship killer, in my eyes...

Hi,
I am trying to port cm12 to this device. It is the first time I am doing although I have previously created custom ROMs by editing system.img, so I am a noob.
I managed to get a stock rom: K50-T5_USR_ST1516_5.654.1_1504152228_MP6V3_CN.rar.
I have slightly modified build/tools/device/mkvendor.sh to be able to work with mediatek files which have a 512 bytes extra header.
I've triedt to create a recovery but I am not sure if it will work as I have some errors in the output
./build/tools/device/mkrecoveryzip.sh /home/vagrant/android/system/out/target/product/aio_otfp /home/vagrant/android/system/out/host/linux-x86/framework/signapk.jar
cp: cannot stat ‘/home/vagrant/android/system//home/vagrant/android/system/out/target/product/aio_otfp/recovery/root/etc’: No such file or directory
cp: cannot stat ‘/home/vagrant/android/system//home/vagrant/android/system/out/target/product/aio_otfp/recovery/root/sbin’: No such file or directory
cp: cannot stat ‘/home/vagrant/android/system//home/vagrant/android/system/out/target/product/aio_otfp/recovery/root/res’: No such file or directory
cp: cannot stat ‘/home/vagrant/android/system//home/vagrant/android/system/out/target/product/aio_otfp/system/bin/updater’: No such file or directory
zip -ry /home/vagrant/android/system//home/vagrant/android/system/out/target/product/aio_otfp/utilities/unsigned.zip . -x *\[* *\[\[*
adding: META-INF/ (stored 0%)
adding: META-INF/com/ (stored 0%)
adding: META-INF/com/google/ (stored 0%)
adding: META-INF/com/google/android/ (stored 0%)
adding: META-INF/com/google/android/updater-script (deflated 51%)
Error: Unable to access jarfile /home/vagrant/android/system//home/vagrant/android/system/out/host/linux-x86/framework/signapk.jar
Recovery FakeFlash is now available at /home/vagrant/android/system//home/vagrant/android/system/out/target/product/aio_otfp/utilities/update.zip
Click to expand...
Click to collapse
Should I copy anything from boot or recovery's ramdisk?
You can find attached the information I've been able to collect (info.txt and build.prop.txt) and build.log which was in a folder in the stock ROM.
Thanks

One Chinese port AOSP to K3-Note.
Its can be daily use and without any bug now. If somebody need it. Just try it.
http://pan.baidu.com/share/link?shareid=2842642895&uk=2251472345
Sent from my Lenovo K50-t5 using XDA Free mobile app

got it in cheinese
can you send a link to an english site?

AOSP
I got some questions
-is it multilanguage
-is it Android 5.0
-gapps included?
-can someone post some screens
Yours faithfully

LeetjeDanhoff said:
I got some questions
-is it multilanguage
-is it Android 5.0
-gapps included?
-can someone post some screens
Yours faithfully
Click to expand...
Click to collapse
-yes
-yes
-only play store but that what important
-maybe later
This ROM is pretty laggy and the ram is mostly full, and the worse part is that it can't play any video or jifs. For now I will recomand not to install this ROM until it will be modify correctly. Link from megahttps://mega.co.nz/#!3UcAkaaK!uEtthUPkeD1q7T4Nyn0MFtpLe9AtwQf-lOwqtz5RU-I

Lenovo K3 Note T50-T5 multilang firmware
This is Lenovo K3 Note T50-T5 multilang firmware: kimmobile "dot" com/tin-tuc/rom-tieng-viet-lenovo-k3-note-k50-t5-lenovo-k3-note-k50-t5-multilang-firmware-id2674

System Update Problem
Hello,
When I go to the the About Phone settings I do not have the option to check for updates on my phone.
Please can you help?
Thank you,
Awais

AOSP based 5.0 build for the K3 Note
Nanj at a Chinese forum had released an AOSP based 5.0 build for the K3 Note
http://bbs.ydss.cn/thread-551335-1-1.html (in Chinese but with captures)
The download link:
http://pan.baidu.com/s/1hqAdrrY
No gapps are included. The build functions ok. Camera, phone / data, and wifi seem to work. However please note that there is an undesirable apk, posed as a system component, at /system/app/SystemServer/SystemServer.apk. It sends frequent packets back to 622b6.romdu.com in China, similar to the issue in another post for a different rom -
http://forum.xda-developers.com/showpost.php?p=55315205&postcount=54
The ROM also comes with a Chinese version of the Opera browser, Oupeng, which also sends analytics packets in the background.
With the two programs removed suspicious packets are no longer obvious from logcat.

headuck said:
Nanj at a Chinese forum had released an AOSP based 5.0 build for the K3 Note
http://bbs.ydss.cn/thread-551335-1-1.html (in Chinese but with captures)
The download link:
http://pan.baidu.com/s/1hqAdrrY
No gapps are included. The build functions ok. Camera, phone / data, and wifi seem to work. However please note that there is an undesirable apk, posed as a system component, at /system/app/SystemServer/SystemServer.apk. It sends frequent packets back to 622b6.romdu.com in China, similar to the issue in another post for a different rom -
http://forum.xda-developers.com/showpost.php?p=55315205&postcount=54
The ROM also comes with a Chinese version of the Opera browser, Oupeng, which also sends analytics packets in the background.
With the two programs removed suspicious packets are no longer obvious from logcat.
Click to expand...
Click to collapse
Does notification led work?

LeetjeDanhoff said:
I got some questions
-is it multilanguage
-is it Android 5.0
-gapps included?
-can someone post some screens
Yours faithfully
Click to expand...
Click to collapse
https://youtu.be/Wf4kkRq0ork review video on the K3 Note

cccho said:
One Chinese port AOSP to K3-Note.
Its can be daily use and without any bug now. If somebody need it. Just try it.
http://pan.baidu.com/share/link?shareid=2842642895&uk=2251472345
Sent from my Lenovo K50-t5 using XDA Free mobile app
Click to expand...
Click to collapse
does it come with gapps?

narithlot said:
does it come with gapps?
Click to expand...
Click to collapse
Sadly, no... But you can flash it with CWM

revert to stock ROM
Lataman said:
I have the same problem, I just changed to new version of VibeUI and had some problems with google apps HELP!
Click to expand...
Click to collapse
you can revert to stock ROM
if you have stock Recovery(Not CWM)
then flash this whith stock recovery
this is official stock chinese/english ROM
https://mega.co.nz/#!MwAxGACR!CNyHABuPxbMpHTHRAhbYJWl_IO4z7jAz8szgIMGt_jQ
instuctions:
make sure you have stock recoveyr
then put this ROM on external memory card
rename the zip file to update.zip
then go to stock recovery select update

New VIBE UI
There has been a new update released by Lenovo.
VIBEUI_V2.5_1524_5.955.1_ST_K50-T5
I have not updated as of yet, for the reason being I am very dissatisfied with the VIBEUI. I currently run 1522, despite the obvious and numerous complications of using the Asian based firmware. I have had to replace the dialer and sms, mms apps as well as install a font manager, even so I am still unable to get 4G working. I would much prefer a pure Android rom and for the past month have been considering beginning a project to build a new Lollipop rom supporting the 67xx MTK chipsets. It would be my first attempt at doing so since all my previous phones have been LG, HTC and NEXUS devices which have always proved easy enough to manipulate and customize.
If anyone out there has experience in building custom roms, especially for devices using the newer 64bit Mediatek chipset, please feel free to contact me. I would appreciate any help offered in this endeavor and I know there are many other MTK device owners out there that are just waiting for someone, or a group of someones', to pioneer a solution for those of us in the western hemisphere using these MTK devices. I am constantly on the look out for new information and projects pertaining to this, additionally I have a dedicated computer with all the SDKs needed to begin the project.
PM me if you are interested in helping kick start this project. Thanks.

What is the significance of this ROM string? I see that "ST" prob means (stable).
Know what "CC", "WCA2" and "WCA8" means in these I found below?
Do you know where is the (official) location to find the latest English language ROM?
My proximity sensor is not working and I'm wondering if moving to a diff ROM will fix that.
VIBEUI_V2.5_1520_7.128.1_CC_K50-T5_WCA2.zip (Android 5.0)
VIBEUI_V2.5_11520_5.827.1_ST_K50_T5 (Android 5.0) <------ the one my phone came with; multi-language
VIBEUI_V2.5_1524_5.955.1_ST_K50-T5_WCA8.zip (???)
VIBEUI_V2.8_1526_7.80.1_CC_K50-T5.zip (VIBE 2.8, Android 5.1)
BurntCircuitz said:
There has been a new update released by Lenovo.
VIBEUI_V2.5_1524_5.955.1_ST_K50-T5
I have not updated as of yet, for the reason being I am very dissatisfied with the VIBEUI. I currently run 1522, despite the obvious and numerous complications of using the Asian based firmware. I have had to replace the dialer and sms, mms apps as well as install a font manager, even so I am still unable to get 4G working. I would much prefer a pure Android rom and for the past month have been considering beginning a project to build a new Lollipop rom supporting the 67xx MTK chipsets. It would be my first attempt at doing so since all my previous phones have been LG, HTC and NEXUS devices which have always proved easy enough to manipulate and customize.
If anyone out there has experience in building custom roms, especially for devices using the newer 64bit Mediatek chipset, please feel free to contact me. I would appreciate any help offered in this endeavor and I know there are many other MTK device owners out there that are just waiting for someone, or a group of someones', to pioneer a solution for those of us in the western hemisphere using these MTK devices. I am constantly on the look out for new information and projects pertaining to this, additionally I have a dedicated computer with all the SDKs needed to begin the project.
PM me if you are interested in helping kick start this project. Thanks.
Click to expand...
Click to collapse

Here where you can find the Rooting and Custom ROMs
https://www.reddit.com/r/lenovok3note/wiki/index
https://www.youtube.com/watch?v=g4PQqRXSUa4
https://www.youtube.com/watch?v=wCwMQkX-1sw

microphone level low - configurable kernel for i9295 ?

On my rooted "samsung galaxy S4 active" (GT-i9295) ... I have been happy with the cm-12.1-20160822-NIGHTLY-jactivelte.zip ... until I used it for telephoning now
The microphone level is really really low. The person on the other end can hardly understand me. And the soundrecorder also has very very low volume.
There are workarounds. I have googled a lot, and found instructions how to root-edit files in /system/ - which all did not help, because one file from the workaround wasn't even existing in my device.
There seems to be another way, using STweaks, but for the above mentioned cm-12.1-... it says "Sorry, no kernel support".
So I am looking for alternatives, please help. Some ideas:
a completely different ROM than the cm-12.1-20160822-NIGHTLY-jactivelte.zip - any chance for an Android 6.0.1 anytime soon?
a different kernel which is compatible with i9295 and my (seems to be newest?) CM12.1, with which I can use STweaks or something similar
another app which allows to change the mic boost level
an instructions manual for cm12.1 which tells me which system files to edit how
your way - what else could I do?
Thanks a lot!

Try CM13.1 https://drive.google.com/drive/u/0/mobile/folders/0B7vmsLnZghSUZ0o0aEtLNUdYR1E