|
|
TNT has 2 new releases for Momo 7:
[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]
I don't think the double tap issue has been solved in TNT 3b, but it is now properly rooted.
Anyone with the skills is free to fix the issue using TNT v3b as base.
Last edited by Dansplans; 02-18-2013 at 09:34 AM.
[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]
I'm not keen on trying it, although I did see someone do it successfully on their momo7 talent in the cube mini forum... but I think that I may have found what is wrong... I went to the root of my tablet in a file browser and then I navigated to sys/class/power_supply and I found two files, one labeled USB and the other battery. I did this on my phone swell (Samsung galaxy ace) and I found three files: USB, battery and ac... my phone is charged the same way as my tablet so I am wondering could this be the source of our battery issues???
By the way, I have checked over on slatedroid and there appears to be a ROM that can be flashed on all rk3066 tablets using cwm, so it is apparently possible... I might try this
We have many CWM ROMs, which can be flashed onto many different tablets. The trick is to get a proper CWM installation onto your tablet to start with.
Many tablet features such as touchscreen, wifi, bluetooth, and battery, are usually built into the kernel. If you flash an incorrect kernel to your tablet, it will become useless until flashed with the correct kernel again.
The issue with battery etc. cannot be easily fixed as there are no complete kernel sources to work with, and decompiling and recompiling kernels can take a very long time, with much trial and error.
One of the reasons ployer tablets seem to have a wider ROM compatibility than most is that ployer firmware appears to be the base firmware used for many other brands. Perhaps ployer manufactures tablets for many other sellers.
To summarize, you can try many flavours of ROMs via CWM, CM10 etc., but these ROMs cannot overcome problems built into the kernel.
[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]
So of rockchip were to release the source code it would make it possible to fix the problems?
Basically, that is correct. Rockchip provides the source code to the tablet manufacturers, who add various hardare modules etc., before recompiling the kernel. Problems and errors become hardcoded into the kernel, and without the original clean sources, devs must spend countless hours stripping out code to find and fix errors.
Usually, we rely on new firmware releases to contain kernel updates and fixes. Some tablet manufacturers release multiple updates and hopefully, everything works properly. Some manufacturers rarely release updates, and some tablet lines never really work 100% properly.
So thank a developer today! Without all of the hard work here and at many other dev sites, many of our tablets would never reach their full potential.
[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]
My experience so far is that all firmware versions except the initial and the shortly followed caixiaoxun dec 1 (dec 3 kernel has broken ov camera module) kernel based 20120903 android builds are bad with the wifi stack
with 121110 (tangyi) and 121203 (caixiaoxun)
wifi stack is perfect it connects really fast but all the newer firmware and ployers android builds seem to have broken it :(
it can take several minutes to connect while with the initial firmware either caixiaoxun or tangyi kernel it takes 6 seconds each time to either connect from sleep or toggle/on off.
does somebody experience the same wifi issues ?
of course it could be router and configuration dependent i guess though for pretty default router settings channel = automatic and g/b compatibility modes it seems the initial firmware works best
The caixiaoxun kernel seems to have severe tearing issues (wrong dvs regulation or compiler error ?)
and tangiy a tad lower performance (yes even with the 1.4 GHz vs 1.2 GHz difference) ?
tangiys kernel in 121110 and 121225 seems really to be most stable so far he was also the first used 121110 and the last used official 121225, though the Android build of 121225 has the wifi connect issues for me and is due to that pretty unusable :(
Also all Ployer Momo7 (speed) ips 1024x Firmware Android builds have broken the Battery Usage Application Display -> Settings->Battery (Battery usage statistics unavailable)
im currently working on my own firmware which tries to take a lot of these general stability issues into account
Last edited by bugmenot; 03-03-2013 at 12:01 PM.
Bookmarks