yashsingh1/xdaforums huggingface dataset:
[Xolo Q700, Q700i] arkerio:
Nice Rom

It feels like m using oppo Phone

only thing i feel is battery drain after few days is very heavy
[Xolo Q700, Q700i] SDShukla:
Thanx A lot bro! :good:
[Xolo Q700, Q700i] SDShukla:
Always Remember-

NOTE- For Seeing Recent App panel You have to Tap Home Button Two Times!
[Xolo Q700, Q700i] arkerio:
Formatted again and battery life is back to awesomeness same as stock :)

Thanx for this Master Piece

Which is best ROm as per you

i find oppo i mean colorOS is baap of all
[Xolo Q700, Q700i] dhanmohan:
i hav installed pxz2..how to install this colors os again? tell me the procedure
[Xolo Q700, Q700i] abhinav2hd:
Dude, just follow the same method you used to flash PXZ,

- reboot to recovery>wipe data & dalvic>install zip from sdcard
[Xolo Q700, Q700i] dhanmohan:
thnx abhinav for help ?

---------- Post added at 09:20 PM ---------- Previous post was at 08:29 PM ----------

r u sure that nothing will happen to my phone... I'm asking again because i already hav custom pxz2 rom bro...
[Xolo Q700, Q700i] dhanmohan:
i installed colors os but boot animation is still pxz2... i changed my boot animation but still showing pure xperia z2 logo on startup
[Xolo Q700, Q700i] abhinav2hd:
That's logo.bin showing up, which will be replaced if Rom contains it.
[Xolo Q700, Q700i] dhanmohan:
Tell me how to change it bro... thnx in advance
[Nexus 5 Q&A, Help & Troubleshooting] medariox:
Hey guys!

I'm using faux123 kernel 007m with intellidemand and the recommended settings for Nexus 5 by faux123 (taken from here: G+: +PaulReioux/posts/gj2v8nVqqfP).

Now I noticed that with intellidemand even the lightest apps are lagging.. is this normal? I also noticed that that often only the first core is active (at 300mhz). With ondemand and the same settings, no lagging at all. Using latest version of FauxClock.

Maybe I'm doing something wrong?

Thank you in advance.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Moresi:
German Menu Option

Hi, I have installed the new Orange Rom on a M5000 and the Contact option menu is in english... I'm installing another M5000 and everything is in english...
[Android Q&A, Help & Troubleshooting] Nasheich Xfiles:
it's maybe just a lag or bugs came from your rom

just don't touch anything for few second then lock again the device using power button
[Eee Pad Transformer Q&A, Help & Troubleshooting] Yharooer:
Hi,

I know there are like 60billon topics about Windows RT running on the TF101 but this is different. (I think)

I was experimenting with QEmu on my Nexus 5 the other day and it run Windows 95 lightning fast, so it got me thinking: would it be (theoretically) possible to emulate Windows XP Tablet Edition/Windows 8 (not RT)/Ubuntu x86/any other x86 OS "almost navitely" on our TF101s? ie Android (or a super-stripped down version) starts up but straight after the boot screen it starts libSDL and emulates the OS of the users choice - or would the TF101 be just too slow (and would need a lot of overclocking) to run a x86 OS?

Just an idea - if anyone has anything to say; like if it's not possible/very slow or if anyone has any idea how - reply!
[Nexus 5 Q&A, Help & Troubleshooting] varuntis1993:
Hey guyz...need some help,

Google now is eating hell lot of battery and is not allowing my device to go in deep sleep mode. I don't want to disable google now but its wake ups in stand by mode are just killing my battery......I have installed appopsxposed and turned off the wake ups, it did work for some days but now it is now back again & taking too much battery.

Also I did tried clearing the cache and data but no help and hotword detection is also turned off.

I m now sick and tired of this thing but don't wanna disable it as it lets me check scores.
[Nexus 5 Q&A, Help & Troubleshooting] PhilipTD:
What you are experiencing is not normal. I keep all Google services, including Google Now, Location Reporting, Google Plus, etc., enabled all of the time, and still get 1-2%/hr. when idle.
[Nexus 5 Q&A, Help & Troubleshooting] ickoicko:
Any BBS log would help. Are you using the newly released Gapps?
[Nexus 5 Q&A, Help & Troubleshooting] PhilipTD:
What's the latest version, please?
[Nexus 5 Q&A, Help & Troubleshooting] ickoicko:
4.1 that's supposed to fix the battery problem of Location Reporting. Here it is
[Nexus 5 Q&A, Help & Troubleshooting] varuntis1993:
I m on rooted stock rom with gravity box, elemantal x kernel and even the location settings are turned off

and google play services 4.1.31

Most of the apps are also greenified.....so I tried my best to get max. battery on stand by but this google search.
[Nexus 5 Q&A, Help & Troubleshooting] Deleted member 5666614:
Is it doing it constantly? I once had the same problem, but it got fixed with rebooting the phone. Google Now drained about 30% in less than 6 hours in my case.
[Galaxy S 4 Q&A, Help & Troubleshooting] der_erdling:
Hello,

So I rooted, or I at least think I did, my I9505. I have installed cwm und the superSU-Update.zip.

Then when I am normally running my device and want to use apps with root access, KNOX denies it. When I start SuperSU, the following message appears: "There is no SuperSU-file installed and SuperSU can't install it. This is a problem. If you switched to Android 4.3, you have to manually root your device"

I have Android 4.3.

So how do I get my root access running?

Thanks in advance for your help,

Best regards, Simon
[Galaxy S 4 Q&A, Help & Troubleshooting] Joku1981:
- I dont think u are rooted by that method

- I dont know if u void ur warranty still. You have here a method for root ur phone without void the warranty: HERE

- For stop knox (when ur phone will be rooted) u only have to install one app (root explorer for ex.) and delete this files:

KNOX in System/App folder:

ContainerAgent.apk

KNOXAgent.apk

ContainerEventsRelayManager.apk

KLMSAgent.apk

KnoxAttestationAgent.apk

KNOXStore.apk

KNOXStub.apk

SPDClient.apk

KNOX in DATA/DATA folder:

com.sec.knox.containeragent

com.sec.knox.eventsmanager

com.sec.enterprise.knox.attestation

com.sec.knox.app.container

com.sec.knox.seandroid

com.sec.knox.store

com.samsung.klmsagent

More KNOX remains:

Folder = Data/clipboard/knox

Folder = system/containers

Folder = system/etc/secure_storage/com.sec.knox.store

Lib = libknoxdrawglfunction.so

File = system/tima_measurement_info ---- TIMA is a Trust-Zone of KNOX
[Galaxy S 4 Q&A, Help & Troubleshooting] der_erdling:
Thanks so far. I now flashed the superSU again and now I have root access, somewhat strange because I am sure I installed the superSU before. I have root access with es file Explorer, but I cannot delete any system apk :/
[Galaxy S 4 Q&A, Help & Troubleshooting] Joku1981:
Install Root Explorer app -> HERE and if u are rooted u will can ;)
[Galaxy S 4 Q&A, Help & Troubleshooting] der_erdling:
Does it make a difference? I activated root access for the es file Explorer
[Galaxy S 4 Q&A, Help & Troubleshooting] Joku1981:
Install Root Checker for see if u are rooted. Good luck :highfive:
[Galaxy S 4 Q&A, Help & Troubleshooting] der_erdling:
Actually I followed every step, except rooting without voiding the warranty. I took your hint that my device probably doesn't have root access und flashed the superSU again, that gave me root (now verified by root checker). Then I tried deleting the files you told me, but that I could not do. I asked if es file Explorer is ok too, because I don't want to spend 4€ when the es explorer works too and there is just another problem why I cannot delete files from my phone storage.

I am glad for every tip you give me :)
[Galaxy S 4 Q&A, Help & Troubleshooting] Joku1981:
Es file Explorer is ok too but maybe u have to give root perms in superSU manually. I use Root Explorer normally coz it takes own root perms :highfive:
[Galaxy S 4 Q&A, Help & Troubleshooting] der_erdling:
I checked again and it has root, but I discovered it is a read only system. I really had that different in mind with my old rooted phone, I thought it worked back then...

Then every Problem is solved for me, thanks alot Joku :)
[Verizon Samsung Galaxy S 4] FriendlyNeighborhoodEnt:
There's no need for n extensive backstory because rooting, flashing, etc I am pretty familiar with, having first rooted the old HTC Thunderbolt.

Now here's what happened:

I have quite a few roms for the S4 but the BoneStock 1.1.4 rom by Andybones always kept bringing me back. I pretty much settled for that one as my dail driver and kept it so for at least 2 months.

Recently in the past week i started getting notifications on my internal sys memory almost out. So i check and realize that my Google Play Music is almost at 6 gb, so I decide to wipe my entire phone just to give it a fresh new flash. Flash goes well, fresh install. I hardly have the time to let my phone die, so I usually just charge it regardless (I have a 5200 mAh extended battery) but this time I decided to let it die. Once it did, i put it to charge immediately and thats when i noticed something was wrong. It was stuck at the battery logo, the animated one that charges while your phone isn't on yet? Well the circle that spins and sort of 'detects' how much battery is left is stuck there. Even if i disconnect my charger it stays there.

So i did what's natural and battery pulled. Did that, reconnected my phone, still the same thing. Now i tried multiple times to get it to turn on and what not but it won't. It gets stuck at the samsung boot logo, no idea why.

So i've decided to call it a night (3 am here, work in the afternoon) and hopefully this thread gets seen by someone who knows how to deal wth this.

TL;DR Clean re-flash of the same daily driver (BoneStock 1.1.4) and let my phone die because I realize I never let it die. Once it does, it get stuck at both the Samsung boot logo, or the animated battery charge circle. I tried accessing recovery, and while I see the little blue message top left hand corner, it just seems to shut itself off, and boot back up only to be stuck again. I have no idea what happeend, I never mess with system functions or any thing of that sort.

The only real solution I see if restoring to stock firmware through Odin? Hopefully that will work, but anyone else experience this before? or something similar and can shed some light on this weird situation?

Thanks in advance!

EDIT: I apologize for the bad grammar, I've been trying to figure this out for the past 2 hours, and it's very late right now.
[Verizon Samsung Galaxy S 4] decaturbob:
I would tend to agree odin the full wipe stock image back and start over
[Verizon Samsung Galaxy S 4] Mightycaptain:
When you see the blue text for recovery do you continue to hold the buttons down until you see the recovery screen? If you take your fingers off it will do what your describing. If you can get into recovery reflash your ROM.
[HTC One Mini] gramateas:
Hello can anyone guide me how can i make battery icons?
[HTC One Mini] gramateas:
I use 2.12.401.1 stock rom
[XPERIA X10 Android Development] Tof37:
As some may know, I'm getting headaches since months (I'm not a professional dev ...) to port 3.0.8 kernel on x10.

I'm opening a new thread to talk about progress on 3.x kernel ported to the

ES209RA..

I'd like to share the work I've made since last year and involve as much people as it's possible.

I'll try to keep this thread updated with "what is working" and a "to do" or "to fix list" ...

You've been warned : this a development thread, and until kernel is "officialy" relased, flashing stuff or adding changes in kernel and flashing it on your device without knowing what you do may damage your phone.

Important notice :

This is not a thread to teach "how to port" or else ...

However when the time will come, testers will be needed, posts will be make to have report etc ...

Don't ask for ETA ...

Thanks a lot for understanding
[XPERIA X10 Android Development] Tof37:
Kernel 3.0.8 porting

Ported on X10 from msm7x30-3.0.x-nAa

Thanks to :

nAa for his sources and his thread to get serial console,

Fxp, Doomlord, Androxyde for there answer to my annoying questions about serial console :),

Achotjan, Feravolt, Scritch and all other who helped me a lot since I started this project.

The link to my repo : Tof37-Github

For now this kernel is just made to be used as a base.

What is working :

Kernel is built with almost all ES209RA drivers (I think ar6000 are missing, nothing else)

it boots

Display is (finally) working

Rom (tested with an old CM9) is booting. Also booting on CM10.1 and 4.2.2 aosp (strange display problem with aosp)

ADB is working (dmesg and logcat can be done)

Battery chatging is working, data and led color are ok too

Got rom display. (Cm10.1 maybe others) ... for a stock configuration it's not so bad ...

Bug list :

QDSP6 has to be disabled, smsm modem is reseting

Recovery key access mismatch (it works only when it wants ...)

Added needed files and lines in defconfig to build ar6000.ko.

Have to port some codes in msm_sdcc.c for plat_disable_wlan_slot and plat_enable_wlan_slot ... seems to be needed to turn wifi on and off ...

Added lines in defconfig to enable bluetooth ... still not working

maybe more I don't even know ...

To do:

Fix known bugs

Had necessary changes in ramdisk
[XPERIA X10 Android Development] Tof37:
Kernel 3.4.0

WIP ... don't fully build
[XPERIA X10 Android Development] FeraVolt:
Thanks :) Nice work
[XPERIA X10 Android Development] Achotjan:
reserved :

thanks tof you are definitly change the future ofxperia x10 ;)

cheers

Achotjan
[XPERIA X10 Android Development] SeC0nduNiT:
i'm ready for testing :cool:
[XPERIA X10 Android Development] Tof37:
Log for qdsp crash

Here is the log I got with qdsp6 enabled :

[ 12.548407] ------------[ cut here ]------------
[ 12.548533] WARNING: at drivers/gpio/gpiolib.c:101 gpio_ensure_requested+0x4c/0xfc()
[ 12.548695] autorequest GPIO-149
[ 12.548766] Modules linked in:
[ 12.548864] [<c0047010>] (unwind_backtrace+0x0/0xf0) from [<c0089af4>] (warn_slowpath_common+0x4c/0x64)
[ 12.549893] [<c0089af4>] (warn_slowpath_common+0x4c/0x64) from [<c0089b8c>] (warn_slowpath_fmt+0x2c/0x3c)
[ 12.559441] [<c0089b8c>] (warn_slowpath_fmt+0x2c/0x3c) from [<c0270708>] (gpio_ensure_requested+0x4c/0xfc)
[ 12.569079] [<c0270708>] (gpio_ensure_requested+0x4c/0xfc) from [<c0270928>] (gpio_direction_output+0x74/0x158)
[ 12.579157] [<c0270928>] (gpio_direction_output+0x74/0x158) from [<c00728ec>] (analog_init+0x18/0x28)
[ 12.588348] [<c00728ec>] (analog_init+0x18/0x28) from [<c0070e40>] (q6audio_init+0x214/0x2e4)
[ 12.596855] [<c0070e40>] (q6audio_init+0x214/0x2e4) from [<c0072490>] (q6audio_open_pcm+0x20/0x200)
[ 12.605883] [<c0072490>] (q6audio_open_pcm+0x20/0x200) from [<c0072b8c>] (pcm_ioctl+0x1d0/0x3f4)
[ 12.614658] [<c0072b8c>] (pcm_ioctl+0x1d0/0x3f4) from [<c01153a8>] (do_vfs_ioctl+0x508/0x584)
[ 12.623158] [<c01153a8>] (do_vfs_ioctl+0x508/0x584) from [<c0115458>] (sys_ioctl+0x34/0x54) MODEM/AMSS has CRASHED
[ 12.631502] [<c0115458>] (sys_ioctl+0x34/0x54) from [<c0042480>] (ret_fast_syscall+0x0/0x30)
[ 12.639903] ---[ end trace 47a718f49542dde2 ]---
[ 12.690778]
[ 12.690789] SMSM: Modem SMSM state changed to SMSM_RESET.
[ 12.691454] Notify: start reset
[ 14.336724]
[ 14.337405] smem: CRASH LOG
[ 14.337410] 'ERR crash log report. Version 2.

In analog_audio.c adding (like KTG .32 kernel)

gpio_request(GPIO_HEADSET_AMP, NULL)

solved the warning ...but not the crash still having :

[ 17.020205] [pcm_out.c:pcm_open] open
<6>[ 17.020852] [q6audio.c:q6audio_init] codecs
<6>[ 17.021094] [q6audio.c:q6audio_init] attach ADSP
<6>[ 17.128602] [dal.c:dal_attach] status = 0, name = 'DAL_AQ_AUD' dal_client d5c24000
<6>[ 17.128795] [q6audio.c:q6audio_init] INIT
<6>[ 17.130021] [q6audio.c:q6audio_init] OPEN control
<6>[ 17.540540] [q6audio.c:q6audio_init] attach ACDB
<6>[ 17.644275] [dal.c:dal_attach] status = 0, name = 'DAL_AM_AUD' dal_client d5eb5800
<6>[ 17.644442] [q6audio.c:q6audio_init] attach ADIE
<6>[ 17.644841] [dal.c:dal_attach] status = 0, name = 'DAL_AM_AUD' dal_client d5eb5400
<3>[ 17.665947]
<3>[ 17.665958] SMSM: Modem SMSM state changed to SMSM_RESET.
<3>[ 17.666632] Notify: start reset

nothing more for now
[XPERIA X10 Android Development] FeraVolt:
Try this in config:

CONFIG_MSM_QDSP6=y
CONFIG_MSM_AUDIO_QDSP6=y //this one wants - SND_SOC_MSM_QDSP6_INTF
# CONFIG_MSM_QDSP6_APR is not set
# CONFIG_QSD_AUDIO is not set

p.s. can you send me your 51-android.rules file.. I messed up usb permissions and adb says:

error: insufficient permissions for device

I have this:

SUBSYSTEM=="usb", SYSFS{idVendor}=="0fce", MODE="0777"

EDIT>nvm.. fixed changing device permissions to 666
[XPERIA X10 Android Development] Tof37:
Will try ;)

BTW think where something is messing ... qdsp6 needs "ac" (qs6audio.c line 971)

pr_info("[%s:%s] attach ADIE\n", __MM_FILE__, __func__);
adie = dal_attach(ADIE_DAL_DEVICE, ADIE_DAL_PORT, 0, 0, 0);
if (!adie) {
pr_err("[%s:%s] cannot attach to adie\n",
__MM_FILE__, __func__);
res = -ENODEV;
goto done;
}
if (analog_ops->init)
analog_ops->init();

res = 0;
ac_control = ac;

but ... if you look at the log on google drive (log 3.0.8 ... boot sur cm9, sans qdsp6)

you'll see that

sysfs: cannot create duplicate filename '/class/power_supply/ac'

I think the problem is there ... if I revert this commit

it doesn't work either cause mx17040 doesn't probe as it should...

let's sleep now :)
[XPERIA X10 Android Development] FeraVolt:
Disable MSM_ION.. I just ported it and got similar thing.. No bootanimation.. All openGles2 apps crashes.. UI glitches.. I'd like to look at how Achotjan ported it.. Maybe its foolish me..
[XPERIA X10 Android Development] Tof37:
Spent nearly the whole day with qddp problem... still crashing...

About display I think memory allocation is not perfect... disabling triple buffer ended with no display but booting rom...

will see that tonight...
[XPERIA X10 Android Development] Tof37:
Some news ...

Have just made a new build with latest adreno drivers ... and voilà !!!

Rom still not usable (flickering, ... ) but things are going on the good way
[XPERIA X10 Android Development] FeraVolt:
Very nice :). Can we have latest dmesg & logcat? And.. maybe you can somehow capture how it's flickering.. To undrstand where the dog lies.. :good:
[XPERIA X10 Android Development] Tof37:
I'll upload the ftf file tonight and the logs as well.
[XPERIA X10 Android Development] blueowl0708:
This is awesome work Tof!

RE: this flickering issue.. I recall Scritch had similar issues when first porting CM10..

http://xdaforums.com/showpost.php?p=34720912&postcount=32

Not sure what Rom you're loading, but perhaps this needs implementing or reversing if you've already included it?

Also: http://xdaforums.com/showpost.php?p=34770510&postcount=37 for slightly more detail.
[XPERIA X10 Android Development] Tof37:
Here is a link to the ftf file with 3.0.8 kernel booting on cm9 rom : here (to flash at your own risk on unlocked bootloader only )

Got a log and dmesg in google drive (check your gmail :) )

EDIT : don't mind about ro.config.disable_hw_accel=false in build.prop ... just something I thought it should be useful ... but no ;)

I have to check that ... I remember this patch ... but took the same msm diplay drivers ... will look :) Thanks
[XPERIA X10 Android Development] blueowl0708:
I thought the patch was for CM10 specifically - so if you're running CM9 while testing......... worth a look anyway! :)
[XPERIA X10 Android Development] Tof37:
;) if you look at kernel .29 git in cmx10 repo, we managed to use the same kernel on ics and JB ......
[XPERIA X10 Android Development] blueowl0708:
Fair does... just a thought :)
[XPERIA X10 Android Development] Aeny:
Not sure if you want some bug reports but here you go. I'll just put the stuff here that's not in OP or second post, I'm probably playing captain obvious anyways. But it's the only way I can help at the moment.

Wifi is not working

offline charging isn't working, device boots straight into android instead.

rebooting from android into recovery gives funky screen drawing trouble in recovery too, recovery works great when booted straight into, this might be a hint where the problem is. seems the rom sets something or some screen buffer is not cleared right. drawing and flipping buffers for double or triple buffering is messed up. CMX10.1 ramdisk + this kernel&rom changes screen behavior to something different but still broken. Might be worth a look too.

To end this post it seems in the posted .ftf file the key to enter recovery is the back key again as it has always been for the ES209RA. (Phone was fooling me.)

GREAT work on the kernel already. Can't wait to see what kind of awesome things this will bring for our devices :good:

~Aeny
[XPERIA X10 Android Development] Tof37:
A little state to tell how things are ...

On cm9 it boots but display need fix ... not the number one in the "to do" list.

The number one is :

On cm10.1 or on AOSP JB 4.2.2 Evervolv based : kgsl-3d0 doesn't open.

Rom is booting but log returns "open(/dev/kgsl-3d0) failed: errno 22. Invalid argument

", with or without new adreno drivers ...

Seems static struct kgsl_device_platform_data kgsl_3d0_pdata and platform_device msm_kgsl_3d0 in the board file needs update ;)

The error in dmesg for max_17040_fuelgauge probe is fixed ... just used the one that is in "old" .29 CMX10 kernel ... did the trick :) Have to update my repo for this.

Thanks for your post.

For the wifi ar6000.ko files are not yet buit ... will do it but I prefer having a clean booting rom first ;)

Didn't try to reboot in recovery from rom ... you're right, screen buffer need to be fix ;)
[XPERIA X10 Android Development] FeraVolt:
what about this:

https://github.com/feravolt/FeraLab/commit/07a097ec23e43b68ca088a5efcd2f7f8c55bccac#diff-1

Theese were ported successfully from enervolv qsd8k .38 kernel who ported them from caf-jb-chocolate and they are using them on kitkat.
[XPERIA X10 Android Development] Tof37:
I saw that on your repo ;) didn't try but this may be an option.

Btw did you update adreno files to use this kgsl drivers ?
[XPERIA X10 Android Development] FeraVolt:
I use them on GB. And no. Since there is no more updates on GB adreno libs those kgsl were doing not so good as the ones i use now.. But i saved a .patch for future.. you may get latest adrenos from qualcomm website..
[XPERIA X10 Android Development] Tof37:
ok.. already updated them to get "something" displayed on cm9 ...

Will have a "little" work to get caf-jb-chocolate kgsl drivers in 3.0.8

Will let you know ;)
[XPERIA X10 Android Development] FeraVolt:
Note that I modified those drivers in my commit so they can match my kernel.. (power managment and clear/outer cache behaviours).. So it may be better if you port them directly from enervovl kernel.. I'm just saying :).. Good luck.
[XPERIA X10 Android Development] Achotjan:
heare we go ION 32bpp and more : https://github.com/Tof37/msm7x30-3.0.x-nAa/commit/e4205f01a5dc0fa73eb9a7ffd8f50bdf31f92e87

cheers

Achotjan
[XPERIA X10 Android Development] Achotjan:
thnak you it will be useful for me ;)

cheers

Achotjan
[XPERIA X10 Android Development] Tof37:
As Achotjan wrote, his commit got Ion and 32 bpp ..

Managed to get kgsl probing but now we have to solve :

kgsl kgsl-3d0: |adreno_waittimestamp| Device hang detected while waiting for timestamp: 6,last submitted(rb->timestamp): b, wptr: 112

The kernel boots on any rom (cm9, cm10, cm10.1, aosp 4.2.2 from Evervolv) but there's no rom display ... the kernel logo is the only thing we see ...

Wip ...

EDIT : according to the line of the log above, something might get wrong in this part of adreno_ringbuffer.c :

int adreno_ringbuffer_start(struct adreno_ringbuffer *rb, unsigned int init_ram)
[XPERIA X10 Android Development] Tof37:
So ... read somewhere that kgsl needs fitting codes in drivers/video/msm ...

I used video drivers from 3.0.8 kernel instead of the ones I put from .32 ... timestamp error diseapeared ;), no more error in rom logcat due to kgsl either.

Have to solve few bugs to use those new drivers with our device and hopefully everything would be nice ;)

BTW solved a small problem in board with smipool memory allocation needed by ion heaps (commited in ion-test branch)

Will clean my repo when I'll get rid of display bugs.

In the same time progressed a little bit in 3.4 build but nothing really new for now.