★★ CROMi-X 7.x Q&A Thread ★★

JOTX10 · Jun 18, 2014

sbdags said:
You don't have to reinstall no. (although reinstalling doesn't take long and you can just install over the top so it will keep all your data)

If you want to reset the resolution open a terminal emulator (install one form the market if you don't have one)

Type the following:

Code:

su wm density reset wm size reset

====================
Hi sbdags,

Thnx, this code works fine and the apps understand the screen-HW again. Is there a way to (re)set the screen to a much lower resolution for sometimes I have to connect the tab to an 'old' monitor and the super resolution 2600x1900 is way beyond their capabilities

Regards,

JOTX10

sbdags · Jun 18, 2014

JOTX10 said:
====================
Hi sbdags,

Thnx, this code works fine and the apps understand the screen-HW again. Is there a way to (re)set the screen to a much lower resolution for sometimes I have to connect the tab to an 'old' monitor and the super resolution 2600x1900 is way beyond their capabilities

Regards,

JOTX10

Yes use the above codes but substitute the first one with dpi you want. And the second with the res like 1920x1200.

Dpi = x resolution / 8

pelago · Jun 19, 2014

You could try YayYouFixedIt's ResUI Resolution Changer App - http://xdaforums.com/showthread.php?t=2716723

DarkCecil · Jul 1, 2014

New digitizer, X-axis inverted

So, I recently broke and have since replaced the digitizer on my 701 (using CRomi-X). But now it seems the X axis of the touch screen has flipped. Every gesture is mirrored along the Y axis. I know a similar problem has occurred with the TF201 as well. I was wondering, is there a possibility of a modded kernel release to compensate for an inverted X axis?
Thanks,

-DarkCecil

sbdags · Jul 2, 2014

DarkCecil said:
So, I recently broke and have since replaced the digitizer on my 701 (using CRomi-X). But now it seems the X axis of the touch screen has flipped. Every gesture is mirrored along the Y axis. I know a similar problem has occurred with the TF201 as well. I was wondering, is there a possibility of a modded kernel release to compensate for an inverted X axis?
Thanks,

-DarkCecil

Do we know what @flumpster did for the TF201 to invert the axis? @that any ideas?

tusker · Sep 7, 2014

sbdags said:
Do we know what @flumpster did for the TF201 to invert the axis? @that any ideas?

It's a simple kernel patch:

diff --git a/drivers/input/touchscreen/atmel_maxtouch.c b/drivers/input/touchscreen/atmel_maxtouch.c
index 30238aa..96a65bf 100644
--- a/drivers/input/touchscreen/atmel_maxtouch.c
+++ b/drivers/input/touchscreen/atmel_maxtouch.c
@@ -1842,6 +1842,8 @@ void process_T9_message(u8 *message, struct mxt_data *mxt, int last_touch)
if (mxt->max_y_val < 1024)
ypos >>= 2;

+ // invert x-axis
+ xpos = mxt->max_x_val - xpos;
stored_x[touch_number] = xpos;
stored_y[touch_number] = ypos;
fingerInfo[touch_number].x=xpos;

The easiest option is to have two different kernels built, and have aroma choose it.

Otherwise, you can create a more dynamic patch, to detect the hardware version of the panel, and invert automatically. I had this patch laying around, but have lost it, so I can't tell you what version to use.

If you compare the dmesg output for the inverted tf201, and a "normal" one, then we can add C code to dynamically invert the x-axis and not have to worry about different kernels.

IvanVd · Oct 6, 2014

x-axis inverted

tusker said:
It's a simple kernel patch:

diff --git a/drivers/input/touchscreen/atmel_maxtouch.c b/drivers/input/touchscreen/atmel_maxtouch.c
index 30238aa..96a65bf 100644
--- a/drivers/input/touchscreen/atmel_maxtouch.c
+++ b/drivers/input/touchscreen/atmel_maxtouch.c
@@ -1842,6 +1842,8 @@ void process_T9_message(u8 *message, struct mxt_data *mxt, int last_touch)
if (mxt->max_y_val < 1024)
ypos >>= 2;

+ // invert x-axis
+ xpos = mxt->max_x_val - xpos;
stored_x[touch_number] = xpos;
stored_y[touch_number] = ypos;
fingerInfo[touch_number].x=xpos;

The easiest option is to have two different kernels built, and have aroma choose it.

Otherwise, you can create a more dynamic patch, to detect the hardware version of the panel, and invert automatically. I had this patch laying around, but have lost it, so I can't tell you what version to use.

If you compare the dmesg output for the inverted tf201, and a "normal" one, then we can add C code to dynamically invert the x-axis and not have to worry about different kernels.

-----------------------------------------
I have the same problem after replacing the digitizer screen of my son's tf701.
I am familiar with rooting and custom roms on my tf201, but writing a patch for this problem is way out of my league!
If somebody could write a patch, i would be grateful!
Than i could root the tf701, and install a custom rom en patch the problem...

norkle · Oct 9, 2014

nvflash backup ?

I know how to perform nvflash / wheelie backup on TF700T.

Does the TF701T have a similar nvflash backup procedure? What should I do to perform full backup prior to update bootloader/unlock/recovery/cromi-x7 ?

A long-time user of CROMi-X on TF700T (and now CROMBi-KK). Anything I need to know about important differences on TF701T?

LucidDementia · Oct 9, 2014

IvanVd said:
-----------------------------------------
I have the same problem after replacing the digitizer screen of my son's tf701.
I am familiar with rooting and custom roms on my tf201, but writing a patch for this problem is way out of my league!
If somebody could write a patch, i would be grateful!
Than i could root the tf701, and install a custom rom en patch the problem...

I imagine you would be one of many grateful folk! I'm in a similar situation; I'm not used to being unable to fix things on my own.

berndblb · Oct 9, 2014

norkle said:
I know how to perform nvflash / wheelie backup on TF700T.

Does the TF701T have a similar nvflash backup procedure?

The short answer is no. There is no nvflash backup for the TF701.

What should I do to perform full backup prior to update bootloader/unlock/recovery/cromi-x7 ?

Backup your personal data.
Unlock and flash CWM.
Make a nandroid of your stock rom.
Wipe
Flash CROMI-X

A long-time user of CROMi-X on TF700T (and now CROMBi-KK). Anything I need to know about important differences on TF701T?

Except for different BL and recovery versions they are very much the same. Only the TF701 runs much better ?

norkle · Oct 9, 2014

berndblb said:
The short answer is no. There is no nvflash backup for the TF701.

Awesome, that's the news I wanted to hear.

berndblb said:
Except for different BL and recovery versions they are very much the same. Only the TF701 runs much better ?

Noticed that already. I have to say _that and sdbags and everyone who contributed to the efforts to improve TF700T's i/o and everything else, did do a fantastic job. Unfortunately the TF700T just got to the point where I couldn't use it for what I needed (heavy lifting of large PDF's and switching between apps a lot). The TF701 is a lot faster even without CROMi-X, but looking forward to the tweaks to come.

norkle · Oct 10, 2014

Up and running on CROMi-X 7.0.3 - anyone else notice a few hiccups?

Unlocked and up on CROMi-X 7.0.3 now. Fantastic work everyone involved.

I had some hiccups flashing the CWM recovery 6.0.5.1 with fastboot, ended up booting to the recovery over fastboot to install CROMi, then later flashing recovery with fastboot worked fine. I think the problem was with rebooting after the flash. I was also working with the tablet in the dock at first. After a few problems I removed it and kept it that way during install. Anyone else seen this?

FWIW, the basic steps were:
* Updated Asus firmware to WW_epaduser_V11_4_1_17_updatelauncher (Android 4.4.2)
* Unlocked with Asus unlock tool
* Fastboot flashed CWM Recovery 6.0.5.1
* CWM Recovery install of CROMi-X 7.0.3

Also at first I was confused by the CROMi-X Aroma installer - it didn't respond to touch. I thought maybe the recovery was causing problems and so I wasted time trying to fix that. After experimenting with Aroma again I realised I could operate it using Vol+/- & Power. Is this normal?

I'm a TF700T CROMi/CROMBi user as well, and so did my Quadrant testing along the way. At this stage I'm not seeing much difference between Asus 4.4.2 and CROMi-X - is this to be expected? I'm using the Stock tweaked kernel and I have disabled journaling (didn't see the journaling make a difference).

I've recorded the Aroma installer options, as I like to keep a record of what I've flashed for if I re-flash (kernels, system vs data apps etc). If I can wrangle tables on here I could post them if anyone is interested.

berndblb · Oct 10, 2014

There is no recovery with touch interface for this tablet. The recovery partition is too small for recovery + necessary drivers. We have to live with the button interface - unfortunately.
Don't get hung up on Quadrant. If it was about speed, I would not have unlocked this tablet at all. For me it's about control and customization options (can't live without forward delete for example)

tcorless · Oct 19, 2014

Just got my tf701t, I love the tablet but the dock not so much. I have the wobble and disconnect form keyboard. I am going to try Joep's kit. I hopes it helps.

But one thing that concerns me, when it goes to sleep when docked, it never wakes up. I have to hold the power button down until it reboots. And when it comes back up it says it is not docked. Anyone else had this?

I have not rooted it yet, could that help with it waking up when docked? Stock is better than my tf700t with its touch screen going bad. I hope it is not a hardware problem with the keyboard. The dock version is DOCK-EC32T-0205, are there other versions that are better or worse?

Thanks
_Tim

IvanVd · Oct 20, 2014

inverted x-axis after replacing touchscreen

tusker said:
It's a simple kernel patch:

diff --git a/drivers/input/touchscreen/atmel_maxtouch.c b/drivers/input/touchscreen/atmel_maxtouch.c
index 30238aa..96a65bf 100644
--- a/drivers/input/touchscreen/atmel_maxtouch.c
+++ b/drivers/input/touchscreen/atmel_maxtouch.c
@@ -1842,6 +1842,8 @@ void process_T9_message(u8 *message, struct mxt_data *mxt, int last_touch)
if (mxt->max_y_val < 1024)
ypos >>= 2;

+ // invert x-axis
+ xpos = mxt->max_x_val - xpos;
stored_x[touch_number] = xpos;
stored_y[touch_number] = ypos;
fingerInfo[touch_number].x=xpos;

The easiest option is to have two different kernels built, and have aroma choose it.

Otherwise, you can create a more dynamic patch, to detect the hardware version of the panel, and invert automatically. I had this patch laying around, but have lost it, so I can't tell you what version to use.

If you compare the dmesg output for the inverted tf201, and a "normal" one, then we can add C code to dynamically invert the x-axis and not have to worry about different kernels.

on my tf701t the touchscreen version = raydium
I found the driver file (in the kernel files- Raydium RM31080 touchscreen driver ) and the code (void raydium_report_pointer(void *p)) where the touch coordinates are captured .
I tried to build/compile stock source to rom but I have many errors where I can't find an answer for.
I want to build a clean version first and flash it to my tf701t for testing, before i compile a changed version.
But i'm stuck in the part where i have to compile a clean version. If I read this forum, it seems so simple... I keep on trying.

IvanVd · Oct 31, 2014

dmesg uitput from a inverted-x-axis-tf701t

tusker said:
It's a simple kernel patch:

diff --git a/drivers/input/touchscreen/atmel_maxtouch.c b/drivers/input/touchscreen/atmel_maxtouch.c
index 30238aa..96a65bf 100644
--- a/drivers/input/touchscreen/atmel_maxtouch.c
+++ b/drivers/input/touchscreen/atmel_maxtouch.c
@@ -1842,6 +1842,8 @@ void process_T9_message(u8 *message, struct mxt_data *mxt, int last_touch)
if (mxt->max_y_val < 1024)
ypos >>= 2;

+ // invert x-axis
+ xpos = mxt->max_x_val - xpos;
stored_x[touch_number] = xpos;
stored_y[touch_number] = ypos;
fingerInfo[touch_number].x=xpos;

The easiest option is to have two different kernels built, and have aroma choose it.

Otherwise, you can create a more dynamic patch, to detect the hardware version of the panel, and invert automatically. I had this patch laying around, but have lost it, so I can't tell you what version to use.

If you compare the dmesg output for the inverted tf201, and a "normal" one, then we can add C code to dynamically invert the x-axis and not have to worry about different kernels.

i place here my dmesg output file from my tf701 with inverted x-axis, maybe someone can use it to write the code????
I'm still trying to write a clean rom...

update: i've build with succes my first bootimage (kernel) that works wit the latest cm11-build, now i can build a new kernel with a modified touchscreen-driver

i've solved my problem wit the inverted x-axis!!!!!
i've changed my driver for the touchscreen en builded succesfull a new kernel!
for anyone who have the same problem, you can test it with a unlocked tf701t, cm11-rom, and using "fastboot boot invx-boot.img" and flash it with fastboot flash boot invx-boot.img"

gparts.com.ua · Dec 9, 2014

THX !!!!

IvanVd said:
i place here my dmesg output file from my tf701 with inverted x-axis, maybe someone can use it to write the code????
I'm still trying to write a clean rom...

update: i've build with succes my first bootimage (kernel) that works wit the latest cm11-build, now i can build a new kernel with a modified touchscreen-driver

i've solved my problem wit the inverted x-axis!!!!!
i've changed my driver for the touchscreen en builded succesfull a new kernel!
for anyone who have the same problem, you can test it with a unlocked tf701t, cm11-rom, and using "fastboot boot invx-boot.img" and flash it with fastboot flash boot invx-boot.img"

Hello friend, thx a lot
as i can see let me suggest you are a speak in russian (Спасибо помогло

)
well just one wish could you please tell me which exactly file did you correct, or even better if you could please share this corrected file here it would be really greate. Thanks in advance. Awaiting your reply ...

berndblb · Dec 9, 2014

gparts.com.ua said:
Hello friend, thx a lot
as i can see let me suggest you are a speak in russian (Спасибо помогло )
well just one wish could you please tell me which exactly file did you correct, or even better if you could please share this corrected file here it would be really greate. Thanks in advance. Awaiting your reply ...

The boot image is attached to the post right above yours

IvanVd · Dec 9, 2014

More info

berndblb said:
The boot image is attached to the post right above yours

the file i've corrected was the Raydium RM31080 touchscreen driver. (rm31080a_ts.c in the kernel map - \kernel\drivers\input\touchscreen)
I changed:

input_report_abs(g_input_dev, ABS_MT_POSITION_X, spTP->usX) to
input_report_abs(g_input_dev, ABS_MT_POSITION_X, (iMaxX - (spTP->usX)))

then i've recompiled the rom

★★ CROMi-X 7.x Q&A Thread ★★

Member

Inactive Recognized Contributor

Senior Member

New member

Inactive Recognized Contributor

Member

Member

Senior Member

New member

Inactive Recognized Contributor

Senior Member

Senior Member

Inactive Recognized Contributor

Member

Member

Member

Attachments

New member

Inactive Recognized Contributor

Member

Similar threads

Top Liked Posts