::: I WILL NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE :::
Hi everyone! Today my Galaxy Tab 10.1 (3G) has been updated to Honeycomb 3.2 via Samsung Kies.
During the update, i saved the Kies download folder containing the firmware.
I've uploaded to 4shared on this link:
http://www.4shared.com/file/IvMsjSLY/P7500ZVVKL1_P7500UBKL1_P7500VI.html
- Its about 727MB.
- You need Odim to flash (I cant help you with that).
- Is a Brazilian VIVO 3G version, and "i think" will work on any 3G Galaxy TAB 10.1.
- I've updated this morning so, not tested enough.
- Is more fast than the original 3.1 but, not fast enough We really need ICS.
Great job tonywalker!
Samsung released updates from gt-p7500 but vivo doesn't offer support.
Many people uses task650's roms, and look very awesome, but most of task650 updates and others works only in "gt wifi only". Is there any way to use these roms and apply 3g support on gt-p7500 from vivo?
Probably not. Developers would have to create a ROM specifically for gt-7500.
After a few days of use I can say that I really liked this update to 3.2. The most annoying problem was resolved, and now just the slowness of the tablet bothers me.
I think you should try.
Thanks a lot.
Searching an restock way for a looooong time, thank you.
which problems and apps?
tonywalker said:
After a few days of use I can say that I really liked this update to 3.2. The most annoying problem was resolved, and now just the slowness of the tablet bothers me.
I think you should try.
Click to expand...
Click to collapse
I´d like to know what kind of problem did you find on 3.2 stock? Is it slowest than 3.1? Yesterday i rooted the tablet (3.1 os) and also overclocked, after these mods i realized that honeycomb are more fast and flow now. Honestly i dont want to create new problems that now.
Some apps are very usefull and cant miss on this tablet like:
- Folder Organize (u can use lite version)
- HD Widgets (improve time and weather with a excelent widget)
- Hide bar (the propose is: hide system bar every time you want, but bottom restore didnt work as the program promess)
- wifi ad hoc enabler (this app are really getting me nervous!!! I´m looking for a app that enable ad-hoc network and share files between pc and tablets (option locked by samsung). This is a new app and most os people are leaving messages saying that its perfect. After follow all the instructions i cant share my files.
** I tried to download 3.2 stock but i think that only 4shared users are allowed to download big files. Please, split the rom in two small files and reupload
Denis Costa
Just to confirm, I flash this by putting my tablet into download mode, then selecting PDA in odin and then search for the .tar.md5 file of the ROM right?
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
Hi,
fews months ago I downloaded a rom called cm_cooper-userdebug-*20150104-*-4.4.4-*.zip, provided by the armv6team, on their own server : {dl,downloads}.androidarmv6.org/. Today, this server is down, and the team seems to stop working. I tried to contact the members, but without succes.
I can find an older rom, but my Cooper is slow whit this one, slow as unusable (near 30 seconds to display the dialer, or 1 minute to display sms ).
I'm looking for this version. Is someone have a copy, or, better, a link for this rom ?
I tried 4 or 5 differents roms, and this one was very the only "kitkat" working well on Cooper.
Thank you for infos.
Hi, I finally switch to the linaro rom : that works fine.
got this error on xposed after upgrading rom, was working fine before upgrading
xposed is not (yet) compatible with android sdk version 19 or your processor architecture (armeabiv7a)"
also this warning message : linker: /data/data/de,robv.android.xposed.installer/cache/app_process has text relocations . this is wasting memory and is a security risk. please fix.
cannot link executable : cannot locate symbol "_zn7android14androidruntime5startEPKcS2_" refferenced by "/data/data/de.robv.android.xposed.installer/cache/app_process "..
sombody know what this means and how to fix it?
MIUI doesn't support xposed module, otherwise it has alternative one, named WSM Tools
Just google and be happy with it
odedaf said:
got this error on xposed after upgrading rom, was working fine before upgrading
xposed is not (yet) compatible with android sdk version 19 or your processor architecture (armeabiv7a)"
also this warning message : linker: /data/data/de,robv.android.xposed.installer/cache/app_process has text relocations . this is wasting memory and is a security risk. please fix.
cannot link executable : cannot locate symbol "_zn7android14androidruntime5startEPKcS2_" refferenced by "/data/data/de.robv.android.xposed.installer/cache/app_process "..
sombody know what this means and how to fix it?
Click to expand...
Click to collapse
Go to en.miui.com, you'll find what you're looking for in the forum section... For mi devices, you'll get better support there...
Sent from my HTC One M9 using Tapatalk
Same error here on CM 11 ...
... seems not MIUI related, on my newest CM11 build from today i get exactly the same error (S4 mini).
Not able to enable Xposed (2.7 exp).
Anyone an Idea ???
regards,
lombartz
Hello,
That is my first post - please correct if I send this to wrong place...
I made a clean new install of LineageOS 15.1 with root and without any Google apps, and I am really impressed with the performance of this ROM.
However, every camera app that I have tried can make only about 20+ photos, then camera app crashes (or if not is not able so save any new picture). Hard reset is needed to fix this situation. I also find that after camera crashes whole system becomes very slow, with very little free memory - the "system" uses about 600MB or more.
I found exactly this situation described in threads about LineageOS 14 for this phone https://forum.xda-developers.com/xperia-t-v/orig-development/rom-lineageos-xperia-t3529556, but is seems that it was never fixed (or I was not able to find the solution). Now Lineage 15.1 also suffers from this bug. For me it looks like memory leak in kernel or driver, but I am not Android developer so I might be wrong.
Is there any solution? And in more general: is LineageOS 15.1 the best (most stable) ROM for this phone?
Thank You in advance,
Michael Widlok