[smokeysworld]

As a new user, I bought the Crystal as it seemed like a good option. I have the Batch 3 and, although I read about the differences, I was still under the impression I could install cyangenmod 10 on to it in order to use the gps usb mouse compatibility along with the bluetooth function as a bonus extra.

It, however, appears I cannot install cyangenmod on to the tablet. I already have it rooted (came as standard). So is there any to get working gps on the batch 3 at all or should I return the tablet?

Thanks.

[fuser-invent]

smokeysworld, on 11 March 2013 - 09:32 AM, said:

As a new user, I bought the Crystal as it seemed like a good option. I have the Batch 3 and, although I read about the differences, I was still under the impression I could install cyangenmod 10 on to it in order to use the gps usb mouse compatibility along with the bluetooth function as a bonus extra.

It, however, appears I cannot install cyangenmod on to the tablet. I already have it rooted (came as standard). So is there any to get working gps on the batch 3 at all or should I return the tablet?

Thanks.

I don't understand, why do you think you can't install CM10? The only batch3 risk is that you might not have a working camera but there should be a comp patch for that soon, I sent Christian mine for Crystal Clear.

Just so you know though, maybe of the "features" like bluetooth or gps are finicky and may or may not work depending on what type of dongle you have.

[smokeysworld]

Hi and thanks for the reply. I get the screen in the attached picture and it says installed but when I reboot, it then shows as the original rom.

On a secondary note, I seem to have ruined it by downloading a boot animation changer from the play store. It boots, shows no animation then the screen only shows 40& of the display. The rest of the screen is black (although it accepts touch inputs)

May need to send it back regardless.

As for bluetooth and gps. I would have asked which ones specifically work and bought those. They are essential as this is for a car pc build.

Thanks again for the reply

Attached File(s)

•  2013-03-11 13.53.40.jpg (300.16K)
  Number of downloads: 23

This post has been edited by smokeysworld: 11 March 2013 - 07:15 PM

[fuser-invent]

Looks like you are either using the wrong recovery or you messed up your internal partitions and they aren't mounting. If you don't end up sending it back then you should head over to the unbricking thread. You might be able to just download TWRP and then flash the internal memory format zip, then try and install CM10 but if that doesn't work you would need to attempt the "soft" brick SD card method first.

[smokeysworld]

Ok, so I have persevered and have made 'some' progress. I did as you suggested and used TWRP and this has allowed installation of the cyanogen rom. I Tried installing cyanogen 10 as it has the bluetooth/gps compatibility (10.1 says bluetooth not working).
and
I installed the last CM 10 build, GApps and the batch 3 compatibility(Crystal (new batch) v1.1)

After doing this, its frozen on the second boot screen (ainol Tab NOVO7 Crystal)

I tried clearing all the cache/factory rests etc but nothing seems to help....

Advice before I return it?

[fuser-invent]

smokeysworld, on 14 March 2013 - 06:28 AM, said:

Ok, so I have persevered and have made 'some' progress. I did as you suggested and used TWRP and this has allowed installation of the cyanogen rom. I Tried installing cyanogen 10 as it has the bluetooth/gps compatibility (10.1 says bluetooth not working).
and
I installed the last CM 10 build, GApps and the batch 3 compatibility(Crystal (new batch) v1.1)

After doing this, its frozen on the second boot screen (ainol Tab NOVO7 Crystal)

I tried clearing all the cache/factory rests etc but nothing seems to help....

Advice before I return it?

Did you get any error messages or warnings in TWRP after while flashing and/or after flashing the internal memory format zip? The SD card soft brick method is in the unbricking thread.

This post has been edited by fuser-invent: 14 March 2013 - 08:30 AM

[smokeysworld]

Not had any errors come up during the flashing process.

The unbricking is not very clear with the batch 3 crystal but regardless, TWRP won't let me select SD card any more and stock recovery says can't get /sdcard.... Getting irritated now, My Galaxy S3 was a doddle to do and never gave me hassles like this!

This post has been edited by smokeysworld: 14 March 2013 - 09:19 AM

[fuser-invent]

smokeysworld, on 14 March 2013 - 09:18 AM, said:

Not had any errors come up during the flashing process.

The unbricking is not very clear with the batch 3 crystal but regardless, TWRP won't let me select SD card any more and stock recovery says can't get /sdcard.... Getting irritated now, My Galaxy S3 was a doddle to do and never gave me hassles like this!

Wait a second. You keep saying you have a batch three but then mentioned you are using a Batch 2 comp zip (Crystal (new batch) v1.1), so do you have a Batch 3 or a Batch 2? It's extremely important that you use the correct TWRP and the correct batch comp zip if really have a Batch 3.

If you are unsure, go back to the CM10 thread, and see the line that says " Crystal (third batch**) rc3 (Use this TWRP recovery) " and the line that says "Third batch crystal came with a different bootloader and are sold with a stock rom dated 1212 (12th of december), anyway just to be sure to identify correctly your crystal follow these instructions from flsuperstore"

[paracetamol]

Thanks, this has come in very useful in a few occasions!

[Hello-]

Hey, thanks for writing this guide on the Crystal. I was able to follow through to try out CM10.1, aokp 4.2 and crystal clear from stock 1119 on a batch 1 Crystal. I really like CM10.1 and would like to run that. The problem is the touch screen is not picking up touch input for 0.5cm on the bottom and on the right edges. This only occurs with CM and AOKP. Are there any tweaks I can do to increase the touch area to fill the whole screen?

[fuser-invent]

Hello-, on 18 March 2013 - 06:05 AM, said:

Hey, thanks for writing this guide on the Crystal. I was able to follow through to try out CM10.1, aokp 4.2 and crystal clear from stock 1119 on a batch 1 Crystal. I really like CM10.1 and would like to run that. The problem is the touch screen is not picking up touch input for 0.5cm on the bottom and on the right edges. This only occurs with CM and AOKP. Are there any tweaks I can do to increase the touch area to fill the whole screen?

It sounds like you are talking about the 20-pixel dead zone. From my guide:

Quote

The bottom of my touchscreen on the stock ROM is not very responsive, sometimes missing inputs or inputting to a different location than where I was touching.
I can barely type on the keyboard, it keeps registering other letters, what can I do?
If you want to check on where your touches are registering on the screen, you can go into "System - Developer Options," turn on the Developer Options and enable "Input - Show Touches." There is a 20 pixel dead zone around the entire edge of the tablet screen where touches are not registered. There is also a major problem with touch sensitivity in stock firmware, so it makes it even more difficult when trying to click things near the edge of the screen. My ROM has several build.prop changes that vastly improve touch sensitivity, so you can always use those build.prop tweaks to improve your tablet, even if you don't install my ROM. There are other improvements as well that improve overall performance, which in turn improves touch sensitivity. Those tweaks require init.d support and you can see the scripts in the system/etc/init.d folder of my ROM.

The problem is a combination of the screen and the touch driver quality. I would be surprised if you weren't getting that in other ROM's as well. I think Christian Troy mentioned working something out with the drivers, to "remove the dead zone" but I don't know if it worked or if anyone tested it and even if it did work, that doesn't necessary mean that area would be responsive. Use the "Input - Show Touches" option to see you are getting it on every ROM, which I'm guessing you are. Let me know if you do find any ROM's that don't have the dead zone, I'd be curious to find out.

[Hello-]

fuser-invent, on 18 March 2013 - 10:10 AM, said:

It sounds like you are talking about the 20-pixel dead zone. From my guide:

The problem is a combination of the screen and the touch driver quality. I would be surprised if you weren't getting that in other ROM's as well. I think Christian Troy mentioned working something out with the drivers, to "remove the dead zone" but I don't know if it worked or if anyone tested it and even if it did work, that doesn't necessary mean that area would be responsive. Use the "Input - Show Touches" option to see you are getting it on every ROM, which I'm guessing you are. Let me know if you do find any ROM's that don't have the dead zone, I'd be curious to find out.

It only happens on CM and AOKP. On stock roms and on your rom the touch circle goes to all edges but jumps around (dead zones) certain parts of the screen.

[fuser-invent]

Hello-, on 19 March 2013 - 08:05 AM, said:

It only happens on CM and AOKP. On stock roms and on your rom the touch circle goes to all edges but jumps around (dead zones) certain parts of the screen.

So on my batch1 Crystal, when I first got it, I only had the 20pixel dead zone on what I think was the bottom and right hand side of the screen. After attempting to fix it with some calibration apps floating around it changed to all four sides of the screen. So I'd recommend not using a calibration app and just counting yourself lucky that you don't have it on all 4 sides. Christian Troy explained it somewhere at some point. The edges of the screen are not very sensitive and that is why the touch circle jumps around and I'm assuming is also why Ainol coded the limit into the touch driver. My Batch1 and Batch2 Crystal both have the dead zone, even on my ROM, so I'm unsure of how you could be not having it on stock ROM's but it's better than having it I guess.

[yash3]

Dear sir,
Im new to novo7 crystal and very new to android.
I want to know something about crystal.
Hope you can help me.
1.My crystal got heat bit more when i turn on it till shutdown without wifi on.is that normal or something wrong on my crystal?
2.My batch no is 130108Gxxxxx ,so as i und it is batch 3 one.how to backup my rom,then i can upload it to any developer want it?
3.I want to connect my 3g dongle to connect to the net.but my tab doesn't recognize the dongle.how can i solve this on stock rom?
4.How can i use bluetooth dongle on this tab?
5.what are the custom roms that suite for my crystal?

Sorry for long questions.but im helpless,In here no 1 got this tablet.

This post has been edited by yash3: 04 April 2013 - 02:37 AM

[Dadoly]

Hi Guys
How to find out witch batch I have couldn't find my build number in this guide, My build number is 20130322 I have ainol novo 7 cyrstal quadcore. I want to install a custom rom if anyone could help me I would appreciate it!
Thanks btw awesome tablet!

[cxz]

Dadoly, on 12 April 2013 - 01:48 PM, said:

Hi Guys
How to find out witch batch I have couldn't find my build number in this guide, My build number is 20130322 I have ainol novo 7 cyrstal quadcore. I want to install a custom rom if anyone could help me I would appreciate it!
Thanks btw awesome tablet!

The custom roms here are for dual core only.
Forum for quad cores: http://www.slatedroi...rm-cpu-devices/

[jjuriss]

Hi! i have problem, I flash rom for batch1 to my crystal batch3, now is tablet dead. if possible some fix it??? thanks for every answer

[fuser-invent]

jjuriss, on 07 May 2013 - 11:02 AM, said:

Hi! i have problem, I flash rom for batch1 to my crystal batch3, now is tablet dead. if possible some fix it??? thanks for every answer

See my unbricking thread in my signature.

[Kazu101]

Thanks for the wonderful guide it will certainly come in handy ;]

[isaacloco]

thanks