Database Develop

[JB 4.1.1][ROW] Just managed to compile

Hello!
I've spend some days to compile JB for TPT ROW 32Gb. And there are the following results:
Works:
--Display. Interface is _very_ smooth
--Pen
--Automatic brightness
--External SD
--USB host
--Bluetooth
--WiFi (Partially: Signal strength indicator broken. Disable avoiding poor networks in advanced menu)
--GPS
--Internal sdcard
Doesn't work:
--Camera
--3G
--Sound
I also had to repack boot image to include configuration changes (init* files).
See attached logcat.
next step I will try to add proprietary source files for Wifi and camera and compile JB again.
==Boot image gzip for flashing with system image using nvflash or dd from recovery==
http://dl.dropbox.com/u/1737679/part07.20120724.img.gz
==System image gzip for flashing with boot image using nvflash or dd from recovery==
http://dl.dropbox.com/u/1737679/part08.20120724.img.gz
Remember to always do a backup copy of your device images before flashing new ones.

Great work mate! I assume that if we want to test this later on our tablets, we need to be rooted?
suntechnic said:
Hello!
I've spend some days to compile JB for TPT ROW 32Gb. And there are the following results:
Works:
--Display. Interface is _very_ smooth
--Pen
--Automatic brightness
--External SD
--USB host
--Bluetooth
Doesn't work:
--Camera
--WiFi
--3G
--GPS
--sdcard fuse mounting
I also had to repack boot image to include configuration changes (init* files).
See attached logcat.
next step I will try to add proprietary source files for Wifi and camera and compile JB again.
Click to expand...
Click to collapse

Woohoo! Look forward to trying this!

This is amazing work! Thank you.
I see Lenovo finally released the ICS source code. Maybe this will help you get some other stuff working.
Also, how were you able to flash your build? Have you not upgraded to OTA3? I'm assuming you still have CWR working.
Thanks again.

Great work, thanks! I'm glad that there is work going on!

Great news! As I installed ota3 before rooting my device, I hope that there will be some way to get cwm and root working...
Sent from my GT-I9300 using xda premium

Very happy that you're working on a new ROM for our device!!!
And I really hope that someone finds a way to root OTA3 since I was also too dumb to do that before updating.
Cheers!

Wow!! Keep up the good work!!!

can't wait, great work!

Great!
I thought I will be first
According to full_indigo device ID, it is AOSP, not CM? Wow..
I think together we could at last make 3G work as other hw are relatively easy to fix(may be not true for camera as sources again changed). I familiar with Qualcomm RIL framework and can't wait to see how it works with tablet and more opensource hardware module..
I also had to repack boot image to include configuration changes (init* files).
Click to expand...
Click to collapse
lenovo haven't packed init scripts? Oo how it works then? ;/
PS: hello from Russia

obscure.detour said:
This is amazing work! Thank you.
I see Lenovo finally released the ICS source code. Maybe this will help you get some other stuff working.
Also, how were you able to flash your build? Have you not upgraded to OTA3? I'm assuming you still have CWR working.
Thanks again.
Click to expand...
Click to collapse
Lenovo released ICS open source code but they forgot to release new kernel sources. This prevents me from building bcmdhd driver instead of bcm4329. It looks like JB is oriented for NL80211 wireless interface and not WEXT.

this isnt for the K1 is it

It's for tpt only

When can we see this in a flashable version? Not to sound pushy, I know we have all see the development slow down.

Are there any other tricks we need to get this up and running? I flashed partition 7 and 8 using NVflash but my tablet is stuck in a boot loop at "lenovo"
EDIT: Is this incompatible with CWM recovery?

What is TPT
Not to sound stupid but what is TPT? I have a K1 as well and am wondering if this will work?

TPT= ThinkPad Tablet

Lenovo released ICS open source code but they forgot to release new kernel sources
Click to expand...
Click to collapse
yes I also tried to get more info but for now no response. At last they released external folder of their custom build, which also contains alsa-audio, as I seen in cm9 device tree, it should fix audio with ease(maybe after patch as sources again changed in JB).
It looks like JB is oriented for NL80211 wireless interface and not WEXT.
Click to expand...
Click to collapse
but WEXT is there isn't it?
Anyway, congrats on working wifi.

Has anyone else got this up and running? I tried uninstalling CWM and reflashing part 7 and 8 but still no luck.

mr toasty said:
Are there any other tricks we need to get this up and running? I flashed partition 7 and 8 using NVflash but my tablet is stuck in a boot loop at "lenovo"
EDIT: Is this incompatible with CWM recovery?
Click to expand...
Click to collapse
Some of existing software probably blocks normal startup. It is always advised to clean dalvik-cache and user data (backup first). It's up to you.
Right after Lenovo logo you should see 'Android: Optimizing applications' or something similar.

Android 4.4 Kit Kat Discussion Thread

This thread is for the developers to discuss the bugs and problems of the kitkat development for the p990.

Nice that you created a thread for kitkat! Really thanks
So for the progress on cm 11:
It is really difficult to find the cause of the dark screen, because we can't get an adb connection to working. The devices don't show up with adb devices
Maybe it is disabled at the moment
We can't take all changes from your slimroms repo, because cyanogenmod toke another way in handling backward compatibility. So for now we have a dark screen with cm 11 and no adb

Here are some of the threads from other tegra2 devices which I'm following:
Galaxy R: link
Galaxy Tab 10.1: link
Captivate Glide: link
Xoom: link
P990: link
Additional T2 devices where I didn't see any Kitkat related threads, yet:
Eee Pad TF101: link
Atrix 4G: link
All still suffer from the same problems, we need some proper workarounds (in frameworks/native most likely) to fix the hot reboots before we can move on to fix the smaller problems.
I've posted in some of them in order to help with other problems (like the set_metadata one where I send the fix to @DJNoXD as well), but I have no idea how to fix the hot reboots currently.
Personally I don't see a use in fixing various stuff as long as the device is too unstable thanks to the reboots (that's why you won't find any 4.4 thread from my so far).
I'm just collecting some information in this thread to have everything together.
Therefore some more stuff regarding the device stuck at boot which we faced earlier as well:
tonyp said:
The only way to fix the blobs would be an update by nvidia / the vendors - which isn't happening obviously.
So you need to workaround the limitations of the old EGL in the sources to re-add compatibility (which btw had to be done for Android 4.3 and partly Android 4.2 as well).
The reason that CM11 doesn't boot up for you is that CM hasn't merged the required patches.
The commits do exist on CMs gerrit though:
http://review.cyanogenmod.org/#/q/s.../android_frameworks_native+branch:cm-11.0,n,z
They're new implementations of the CM10.2 patches by arcee.
Note that in some first tests the new ones didn't work for me on my tegra2 phone anymore - somethings seems to be broken in them for the tegra2 architechture.
The OmniROM has (had? I think they partly reverted it here) used forwardports of the old CM10.2 patches - which the SlimROM has merged as well in a similiar manner.
But this only fixes booting, I still do have way to many hot reboots so some more stuff has changed in 4.4 - which I didn't manage to fix or workaround so far.
What we need is someone with that kind of deep hardware knowledge.
All in all: Blindly changing blobs or other libs won't help here at all. Just building against different framework/native trees won't either.
The surfaceflinger and probably some more stuff in frameworks/native needs to get worked on in code.
Currently there doesn't exist a tegra2 device which fully works to my knowledge - and I'm following a couple ones like the Galaxy R, the Xoom, the Transformer TF 101, the Atrix and the Galaxy Tab 10.1.
I'm working on the 2x, but have way too less time at the moment to dig any deeper into the code - while the current ROM boots (using my frameworks/native repo here) and has a working ril, wifi & storage it's nowhere near a daily driver thanks to frequent hot reboots.
Click to expand...
Click to collapse
Edit: Reminder: Do not spam in this forum section!
I will delete all "thanks" posts or similiar non-development related ones without a comment.

When i use the sources for frameworks native from @DJNoXD, i have less then 2 hot reboots a day. I even use it as daily driver with a work around for wifi.
I think if we could find the commits that broke the stability we could search for a work around or fix. I already tried it only for the sufaceflinger but i had no success, because it still worked properly, so it maybe is related to libgui or i think libui?
Took me hours for the surfaceflinger, so it will take even more time for all other in framework native. When i found some time during the week, i will try.
But KitKat is awesome related to RAM, Multitasking and performance.
Gesendet von meinem LG-P990 mit Tapatalk

Evervolv frameworks/native etc were no help getting the tf101 to boot omni. So far we're at Boot Animation
thx to
kishoreinme said:
Having the 3 perfhud .so files in /lib/egl/ causes this. Delete them and it boots
Click to expand...
Click to collapse
from this thread: http://forum.xda-developers.com/showthread.php?t=2517719&page=9
http://forum.xda-developers.com/showthread.php?t=2489841&page=7
Firtecy said:
When i use the sources for frameworks native from @DJNoXD, i have less then 2 hot reboots a day. I even use it as daily driver with a work around for wifi.
Gesendet von meinem LG-P990 mit Tapatalk
Click to expand...
Click to collapse
Is that the frameworks from slimrom or from https://github.com/DJNoXD/frameworks_av1 ?

dlumberg said:
Is that the frameworks from slimrom or from https://github.com/DJNoXD/frameworks_av1 ?
Click to expand...
Click to collapse
These are the repos that I use for slimrom:
https://github.com/p990-slimrom/

Here is the GalaxyR Omni 4.4.2 development link
http://forum.xda-developers.com/showthread.php?t=2576793

Eeeeh, have I been gifted with a special P990?
I've flashed Tonyp's 4.4 build named cm-11-20131213-UNOFFICIAL-p990 and I am pretty much facing no bugs. Only bug I could find on this fine evening was that USB doesn't get mounted, it charges when connected though.
Sound works, camera works, external SD card works, WiFi works, I bet GPS works but testing that will have to wait till the morning. All of this is on a clean CM11 build without doing any modifications at all. I too am still shocked over this and since I couldn't believe it myself, so I figured I'd post a video bringing this to light.
Short YouTube footage of my P990 running KitKat: YouTube
Could someone do a full wipe and see what they come up with by flashing that same build? It seems rather surreal if 4.4 only works this well on just my phone.
Please note, I have not been under the developmental processes of this project. This is simply testing - all credits to the developers!

USB tether will not work under windows because there are no drivers found. And it works fine under linux. How to fix the hardware id (vid,pid)?
Sent from my XT875 using XDA Premium 4 mobile app

OMAP4 Bluetooth 4.0 BLE

it seems that is working, tried it on 4.4.2, but no OAD support..
to enable it add the following line to android/system/device/motorola/omap4-common/common.mk
frameworks/native/data/etc/android.hardware.bluetooth_le.xml:system/etc/permissions/android.hardware.bluetooth_le.xml
next to
frameworks/native/data/etc/android.hardware.usb.host.xml:system/etc/permissions/android.hardware.usb.host.xml \
and (device specific) system/device/motorola/maserati/bluetooth/bdroid_buildcfg.h
#define BTA_DM_COD {0x1A, 0x01, 0x14}
#define BTIF_HF_SERVICES (BTA_HSP_SERVICE_MASK)
#define BTIF_HF_SERVICE_NAMES { BTIF_HSAG_SERVICE_NAME }
#define PAN_NAP_DISABLED TRUE
#define BLE_INCLUDED TRUE
#define BTA_GATT_INCLUDED TRUE
#define SMP_INCLUDED TRUE
after
#define BTM_DEF_LOCAL_NAME "Motorola Droid 4"
tried with new bluetooth firmware from https://github.com/TI-ECS/bt-firmware, is working but is not stable.
the default firmware is working well with the sensor tags

lucize said:
it seems that is working, tried it on 4.4.2, but no OAD support..
Click to expand...
Click to collapse
Great
I've just pushed your changes to my repositories, so they will be included in tomorrows nightly.
Merry Christmas,
Michael

Merry Christmas to everyone !
All devices that have the TIInit_10.6.15.bts firmware should work so maybe this would be of help for someone else, maybe you can talk with Hashcode or David to enable it on every device. 4.3 should work too !
Regards

lucize said:
All devices that have the TIInit_10.6.15.bts firmware should work so maybe this would be of help for someone else, maybe you can talk with Hashcode or David to enable it on every device. 4.3 should work too !
Click to expand...
Click to collapse
Ok, short gerrit crash-course
Configure your local git to commit with the name and email-address you want to be visible in public repositories
Create an account on http://review.cyanogenmod.org/
Upload an ssh public key there
Clone the repository you want to change with something like:
Code:
git clone ssh://[email protected]:29418/CyanogenMod/android_device_motorola_omap4-common
(This is not necessary if you are working on a direct CM clone and have no other changes in your repository)
Make your changes, commit them
Push your changes to gerrit:
Code:
git push ssh://[email protected]:29418/CyanogenMod/android_device_motorola_omap4-common HEAD:refs/for/cm-11.0
This will tell you an URL where your change is visible.
Go to that URL and add reviewers to your change. For example: Hashcode, David Hacker and probably me (Michael Gernoth)
If your change is acceptable, it will get merged into the CM repository
That's all, no great magic
For more info, have a look at: http://review.cyanogenmod.org/Documentation/user-upload.html
Best regards & thanks for your work,
Michael

lucize said:
Merry Christmas to everyone !
All devices that have the TIInit_10.6.15.bts firmware should work so maybe this would be of help for someone else, maybe you can talk with Hashcode or David to enable it on every device. 4.3 should work too !
Regards
Click to expand...
Click to collapse
Is that firmware part of CM11 or something that I'd have to install manually onto my Droid 4? If so, how does one upgrade the Bluetooth firmware?

bofis said:
Is that firmware part of CM11 or something that I'd have to install manually onto my Droid 4? If so, how does one upgrade the Bluetooth firmware?
Click to expand...
Click to collapse
is part of cm11, you can find it in /etc/firmware/
you can find it here
https://github.com/TI-ECS/bt-firmware/commits/master this is the history page where you can find various versions, but the last version from December won't load and the rest will not work with the headset (no sound)
htc one x has the same bluetooth chip and has a newer version of firmware, but the sound on headset will not work either, everything else seems to work
you can see the version at the beginning of the file, motorola has TI_P6_15.56
to update, turn bluetooth off, simply overwrite the file and the turn it on again.

I noticed that this eventually made it to CM11 for all of Moto OMAP cousins, except for the Bionic (Targa). Any reason that the Targa was left out? A lack of hardware support, or was it just never tested?

guyincog said:
I noticed that this eventually made it to CM11 for all of Moto OMAP cousins, except for the Bionic (Targa). Any reason that the Targa was left out? A lack of hardware support, or was it just never tested?
Click to expand...
Click to collapse
I don't know if it has the proper chip but the firmware is correct so it should be possible. I don't have one to test.
Regards

lucize said:
I don't know if it has the proper chip but the firmware is correct so it should be possible. I don't have one to test.
Regards
Click to expand...
Click to collapse
Thanks for the reply. I've got one, maybe I'll see if I can talk one of the builders for the Bionic will make a test build with the necessary common.mk change.
I apprciate the work on this, and the kernel update you've got in progress. Any extra features we can add to these old devices is a huge bonus.

This might be the wrong place to ask this, but does CM11 or CM11 on our phone support the APTX codec via Bluetooth?

bofis said:
This might be the wrong place to ask this, but does CM11 or CM11 on our phone support the APTX codec via Bluetooth?
Click to expand...
Click to collapse
it has the hardware support
http://www.aptx.com/product/motorola-razr-maxx-smartphone
but don't know about the rest of the things

[5.1.1][LMY47X] OmniRom UNOFFICIAL

Whats working:
Bluetooth
Wifi
Not working
Audio
Bad Mapped ouya controller
Lines in screen
Cut screen
Download:
OmniROM: http://www.mediafire.com/download/3cx4dj211rbdd5c/OmniROM-5.1.1-20150517-cardhu-HOMEMADE.zip
Souce code:
OTA App: https://github.com/werty100/android_packages_apps_OpenDelta (not configure jet)
kernel:https://github.com/werty100/android_kernel_ouya_cardhu
Device tree:https://github.com/werty100/android_device_ouya_cardhu
Vendor:https://github.com/werty100/android_vendor_ouya_cardhu

Changelog
CHANGELOG:
ALPHA:
Repo sync omni rom
Prebuilt kernel
2015-05-16:
Antutu 22.000
Kernel build
Update some Blobs with nexus 7
New HDMI permissions LP
Fix sound settings
2015-05-17:
OMNI vendor stuff
Some changes in kernel
Improve stability and speed
Other workaround for sound
2015-05-19:
IN PROGRESS
TWRP settings
LZMA compression in kernel
4.7 arm by default
Audio new config
Omni dependecies with 4.7 arm
Fix building OMNIRom complitly

Maybe I fix some WIFI problems in new build and audio oned
WIFI problems fixing now is connecting to encrypted ones...
Lines apeared graphic gliches or my ouya ?¿ Please some test it
More testing....
Audio still the same
Fix random frezzes and reboot....

werty100 said:
Maybe I fix some WIFI problems in new build and audio oned
WIFI problems fixing now is connecting to encrypted ones...
Lines apeared graphic gliches or my ouya ?¿ Please some test it
More testing....
Audio still the same
Fix random frezzes and reboot....
Click to expand...
Click to collapse
https://source.android.com/devices/tv/HDMI-CEC.html reading this....

werty100 said:
https://source.android.com/devices/tv/HDMI-CEC.html reading this....
Click to expand...
Click to collapse
Corrected please this should be the problem with audio and lines new changes in LP at less audio should be fix

werty100 said:
Corrected please this should be the problem with audio and lines new changes in LP at less audio should be fix
Click to expand...
Click to collapse
New build with HDMI new adroid stuff...
I have tested it with ro.hdmi.device_type=4 and it is not working i have no more time and i have uploaded new build with ro.hdmi.device_type=0 for someone to test it.

Does this work for the black edition ouya?
-Edit-
Will go ahead and test for myself. Thank you! BTW I posted the CM-11 rom you were asking about in the other thread. Sorry I didn't get on sooner. All I did was copy firmware from stock ouya into update zip and bluetooth started working.

I need help with audio and also to take logcat i cant take them

werty100 said:
I need help with audio and also to take logcat i cant take them
Click to expand...
Click to collapse
Today no build but i am progresing audio and lines problem and triying to fit twrp on ouya and fix build to complete and also if all this work becoming official omni(i need to talk with them)

werty100 said:
Today no build but i am progresing audio and lines problem and triying to fit twrp on ouya and fix build to complete and also if all this work becoming official omni(i need to talk with them)
Click to expand...
Click to collapse
Making new build with fixes i figure that lines at less should be fix and we have problems with twrp for making it fit using lzma lest see:fingers-crossed::fingers-crossed::fingers-crossed:
Seems that twrp at the moment cant fit ouya working on it...
And working on getting ouya otas zips
And in few minutes i will test build

Overclocking the Ouya has been known to over heat. You may need to replace the heatsink. http://www.eternityproject.eu/topic/1114917-hardware-modding-for-ouya/

Does this utilize the boot menu and start the boot IMG off of /system like the cm11 builds did?

I mapped my Ouya controllers to my Nexus Player running 5.1.1. I'm assuming the mapping should work on this ROM as well. I can share the file that I used and modified to get it to work when I get home.

There is a full set of keymaps available for download in the cm11 thread. I have used it to get my ouya controller working with several ROMs on different devices.

Excited
I'm so happy this ROM is in development. Was worried the OUYA was dead. Keep up the great work guys.

@werty100 - Good on you! Amazing work.
This is what a real developer is like.
Happy to see you around here.

frickinjerms said:
Does this utilize the boot menu and start the boot IMG off of /system like the cm11 builds did?
Click to expand...
Click to collapse
Yes it is using boot menu but now i am having roblems no build now is booting i dont know why is so stupid

Making new release hop it works

Good luck!

hi,
any experience with this rom from somebody?
is it possible to install the current kodi.tv v15 on it?
does it work?
thx

Reversed audio channels [SOLVED]

Welp since Motorola apparently can't tell left from right I now have reversed stereo in both the headphones and speakers after updating OTA to marshmallow. Looking around it seems to be a common problem. My question is, is there a no-root fix for this? Or alternately is there an easy root fix, without flashing any custom roms?
EDIT: Okay, got ya fix right here if you're rooted: go here, say thanks, rename that file to mixer_paths.xml, copy it to /system/etc & reboot.

What's the build number of yur ota ? latest MM (at least ofr xt1072) build is 24.65-34, i ask that becouse i saw a screenshoot of the retGB ota and was behind that one from the full image. Maybe it's fixed in the latest build.
Wich phone you have ? xt????/ret??, can you check under settings-info please ?

dr.nic said:
What's the build number of yur ota ? latest MM (at least ofr xt1072) build is 24.65-34, i ask that becouse i saw a screenshoot of the retGB ota and was behind that one from the full image. Maybe it's fixed in the latest build.
Wich phone you have ? xt????/ret??, can you check under settings-info please ?
Click to expand...
Click to collapse
XT1072 reteu, Polish. Same build number as in your image. You mean there's another patch out there?

Confused the system version whit the build number /facepalm, my bad, they looks the same.

Ha, no worries. I found a fix tho, check OP.

Speaker and headphones stereo reversed (fix)
In case anyone is interested, the attached file includes both the original mixer_paths.xml and another one modified by me.
The latter is based on the file mentioned in the OP and also on the file included with the Official CM13.0 for our device.
I noticed that headphones stereo channels were also reversed and this is my attempt at fixing it, as I couldn't find any alternative to the post linked in the OP.
I am using this mod for a few days and everything seems fine.

I am on a spreadtrum sc7731 SoC and running a Custom Lollipop ROM ported by me, but I am getting reversed Stereo. And there is no mixer_path.xml in etc folder. How to fix this ? ☺