Ice Cream Sandwich for the TF101
Homepage
Bug Tracker
Source
You might also like to read my blog post which started this and has some bad photos of it running.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Usual disclaimer applies: if you brick your tablet, it's not my problem!
Builds:
20120219 - NvFlash or CWM
Improve touchscreen responsiveness
Gyro & accelerometer support
Fix hardware video decode support
Re-add calendar app
Update GApps20120211 - NvFlash or CWM
Fix touchscreen hang/death/brokenness
Remove mobile signal icon from system bar
Fix superuser settings crash
Revert a graphics hack no longer necessary with the newer nvidia drivers – potential speed up
Update GApps20120209 - NvFlash or CWM
Fix tablet wakeup bug, it stays asleep now
Fix screen corruption during early boot
Battery meter returns
CWM update zip clears caches, still do a factory reset (ie. format /data) if coming from honeycomb20120201 - NvFlash or CWM
Suspend improvements, now uses LP0, but still likes waking itself up
Backlight fixed
Storage settings no longer crashes
USB device improvements, MTP indicator etc
USB drives & micro SD cards mount, images visible in gallery etc.
CWM update zip now just writes everything as a blob, should avoid all previous zip-related problems
Graphics drivers updated to those from nVidia’s ventana devkit ICS release
Includes Google apps20120121 - NvFlash or CWM
Suspend improvements (still needs work)
Headphones should work properly
Improve CWM update zip to cope with mounted /data20120112 - NvFlash or CWM CWM, CWM mirror
Initial audio support (still needs work)
Bluetooth working
WiFi MAC address fixed
Rooted
USB fixes
Include a CWM update zip version (be careful, remember only use if you can flash back honeycomb)20120110
Using a 2.6.39 kernel
Orientation defaulting to landscape
RAM size fixed
Hopefully fix suspend20120106
Fixed WiFi20120105
Initial build
Pm me the link ill post it
Sent from my MB855 using xda premium
http://www.paulburton.eu/2012/01/ics-on-the-transformer-tf101-because-exams-are-boring/
all rights to paulburton
Looks great, keep up the good work! Hopefully you'll get more working soon.
Thank you for your work, keep it up
excellent work.
Sent from my Nexus S using xda premium
inimitableac said:
Pm me the link ill post it
Click to expand...
Click to collapse
Thanks guys, honighamster got there first (and apparently I can't even quote a link...) If anyone does try it be sure to get the images from after the update at the bottom of the post.
Have you considered working with the other devs on this? There is a pre alpha thread in the dev section if you work together maybe you can get something more stable cooked up.
Novarider said:
Have you considered working with the other devs on this? There is a pre alpha thread in the dev section if you work together maybe you can get something more stable cooked up.
Click to expand...
Click to collapse
That's possible, but communicating the current state & maintaining a repository seem like they'd just be boring and slow me down at the moment. Don't get me wrong, I do plan to upload the source but I'd rather get it working better first. There's also the touchscreen bodge I mentioned, which though it works I'd never consider committing to a public repository! It doesn't look like the other build has anything I don't, but it is missing some things I have (wifi, touchscreen, no green screen etc).
paulburton said:
That's possible, but communicating the current state & maintaining a repository seem like they'd just be boring and slow me down at the moment. Don't get me wrong, I do plan to upload the source but I'd rather get it working better first. There's also the touchscreen bodge I mentioned, which though it works I'd never consider committing to a public repository! It doesn't look like the other build has anything I don't, but it is missing some things I have (wifi, touchscreen, no green screen etc).
Click to expand...
Click to collapse
Oh come on, don't pull a CyanogenMod on this. Collaboration is always good, and having multiple people work on the same things in parallel is just useless. Even if you do spend some time for the initial setup, all you'll have to do later is git commit && git push.
Sent from my HTC Desire using XDA App
K900 said:
Oh come on, don't pull a CyanogenMod on this. Collaboration is always good, and having multiple people work on the same things in parallel is just useless. Even if you do spend some time for the initial setup, all you'll have to do later is git commit && git push.
Click to expand...
Click to collapse
I'm not sure you realise how much is involved, it's not just a commit & push because android isn't just one git repository. I've put my device tree on github (still can't link to it, but my username there is the same as here) in the device_asus_tf101 repository. However, you still won't be able to build everything because you're missing the binary blobs etc, and if you pull them from my build the touchscreen still won't work because the bodge I mentioned is in frameworks/base. Please be patient!
paulburton said:
I'm not sure you realise how much is involved, it's not just a commit & push because android isn't just one git repository. I've put my device tree on github (still can't link to it, but my username there is the same as here) in the device_asus_tf101 repository. However, you still won't be able to build everything because you're missing the binary blobs etc, and if you pull them from my build the touchscreen still won't work because the bodge I mentioned is in frameworks/base. Please be patient!
Click to expand...
Click to collapse
I understand that, I just hope you and other developers work together, something that seems difficult at the start but will pay off farther away. I'm not a skilled Android developer, but I'm familiar with Linux (being a distribution maintainer and developer) and I know how important the community is and how collaboration can be neglected at first.
Sent from my HTC Desire using XDA App
I agree, I'm not a dev but I have installed 50 or more custom roms on four different phones and two tablets, and any single dev rom I've ever flashed never felt complete or smooth. Other people may propose different and possibly better ways to fix certain issues, maybe that they have encountered and you haven't perhaps. Just saying even Einstein collaborated with other scientists and Steve Jobs collaborated with other software designers. It could only benefit the project overall, especially if you dictate the respective roles of the devs assisting you..that seems to be the whole point here on xda, not just 'look what I wrote or 'help me fix this but more community, and that's what encouraged me to sign up. I doubt I would have if I didn't also have the opportunity to learn about how the software is being designed rather than 'here is some software. In fact, I don't flash any rom that isn't reviewed and discussed by more than two people on this forum, and I won't flash yours until there is a detailed list of features and bugs, it's a safeguard I do to keep from flashing abandonware, and I just can't see one guy being able to do everything needed to get a working ICS rom up, not saying anything about your skills etc. But when I was a tattooist, I used to practice on myself, and after discussing my ink with an old timer and showing him what I needed to fix he asked 'do you want your tattoos done by yourself, or do you want them done right?' Good luck, I can't wait to try it out when more people get it installed and a list of bugs/fixes is posted!
luna_c666 said:
I agree, I'm not a dev but I have installed 50 or more custom roms on four different phones and two tablets, and any single dev rom I've ever flashed never felt complete or smooth. Other people may propose different and possibly better ways to fix certain issues, maybe that they have encountered and you haven't perhaps. Just saying even Einstein collaborated with other scientists and Steve Jobs collaborated with other software designers. It could only benefit the project overall, especially if you dictate the respective roles of the devs assisting you..that seems to be the whole point here on xda, not just 'look what I wrote or 'help me fix this but more community, and that's what encouraged me to sign up. I doubt I would have if I didn't also have the opportunity to learn about how the software is being designed rather than 'here is some software. In fact, I don't flash any rom that isn't reviewed and discussed by more than two people on this forum, and I won't flash yours until there is a detailed list of features and bugs, it's a safeguard I do to keep from flashing abandonware, and I just can't see one guy being able to do everything needed to get a working ICS rom up, not saying anything about your skills etc. But when I was a tattooist, I used to practice on myself, and after discussing my ink with an old timer and showing him what I needed to fix he asked 'do you want your tattoos done by yourself, or do you want them done right?' Good luck, I can't wait to try it out when more people get it installed and a list of bugs/fixes is posted!
Click to expand...
Click to collapse
Community is great, and if anyone wishes to work on something the device tree should be enough for them to do so. I'll get the kernel source out too but at the moment I'm using 2.6.36 and need to port to 2.6.39, so I'll probably wait until after I get that running. (If anyone's really desperate for the current kernel it's basically ASUS stock with one patch to the tegra overlay code, which I'd link to if I could post links...).
I'm fine with you not flashing it, you don't sound like the audience at the moment anyway - once I get the rest of the hardware working that'll change... I posted this just because I expect there'll be some people who want to see it running despite its many flaws, and as I fix them I expect more people will be interested. If I'm wrong and nobody wants to try it then that's fine too, I still get ICS on my tablet and I'm happy.
It might sound arrogant, but I can handle getting this thing working. I've done a fair bit of android work and much more complicated stuff than a device port. Just give me a bit of time
Nice work Paul. Keep up the hard work!! It seems you have gotten further than some, or even most, at this point from what I've been able to gather. Of course, I am not sure exactly how much is working from Asus' official build, but I think they are probably a bit nervous seeing that there are other devs (such as yourself) that may or may not be further along with it than they are. I would venture a guess to say that Asus is probably beta testing already, especially seeing the size of the company and the amount of people rumored to be working on this. Anyhow, thanks for the effort and happy building.
sent from my ASUS Transformer running Prime 2.1.1 using Tapatalk
Is a flashable zip available? Nice work
Anyway, is the ICS browser faster than the HC's one?
Great job! But now I have a question - how can I flash HC 3.2.1, i.e. Prime? If I just flash it from CWM asus is not booting, but I don't want to lose my files on sdcard with flashing nvflash, so is it any other way of installing HC?
Sorry for my language
Do you have hardware acceleration working? How did you fix the touchscreen?
A_new_person said:
Great job! But now I have a question - how can I flash HC 3.2.1, i.e. Prime? If I just flash it from CWM asus is not booting, but I don't want to lose my files on sdcard with flashing nvflash, so is it any other way of installing HC?
Sorry for my language
Click to expand...
Click to collapse
You can flash just boot.img & system.img (partition 6 & 9 respectively) by doing something like this:
Code:
./nvflash --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync
./nvflash --resume --download 6 boot.img
./nvflash --resume --download 9 system.img
./nvflash --resume --sync --go
You might need to (ie. probably should) clear userdata too, which I'm sure CWM will let you do. Your sdcard should remain intact (but don't blame me if it doesn't!).
Take it outside to other threads gents and let the guy focus on his ICS port.
Sent from my Transformer TF101 using Tapatalk
Related
Hi!
Since last week, I've been working on an usable kernel for the HTC Vox. I guess you've already looked at this post: http://forum.xda-developers.com/showthread.php?t=368014&page=5
More or less, I have a working kernel. I've tested some images against the modified kernel, and both Gpe and Opie get to the welcome screen (without getting stucked). Nothing is really usable, as they're not even compiled for this specific platform (cannot get to compile opie for arm by myself... yet), but as a base, it's not bad at all.
As I've seen on my previous post, there's people interested on this (3300 views make me believe that), what I would want to know is, are there more developers interested on building a linux port for the Vox? Testers will be needed also, but later, when we get to something useful for testing
If you're interested, reply!
Cannot help u develop anything here, but would be a willing tester for it... thoroughly
I'd love to help, but I'm in the middle of moving to a new place and won't have internet most of the time next 2 weeks.
Do you have a Wiki or other place for collaberating? SourceForge perhaps?
I do have a wiki, but upload is no faster than around 80kB/s
In case you haven't seen it, you have a new build of the kernel on the other post, along with links and a little manual to start a graphic environment on the vox.
@barth666, @StefanHamminga
I've been thinking about it, and... I don't know what to do I mean, I think Sourceforge is the best place to dump it all, and it gives us a wiki too. On the other side, here is the xanadux wiki, and maybe it would be a good idea to let sourceforge host the files, and leave the wiki in here with other HTC phones... what do you think?
Oh! For GPIO dumping, the only thing I've seen working is the linwizard project's Haret_Omap.exe (in case you want to try to guess where the damned keys are )
PS: Anyone has an HTC Tornado? I'd love to know if the tornado kernel makes the leds and vibrator flash, I can't find where they are!
biktor_gj said:
PS: Anyone has an HTC Tornado? I'd love to know if the tornado kernel makes the leds and vibrator flash, I can't find where they are!
Click to expand...
Click to collapse
I have a tornado (and vox and wings), so tell me what to test
I know from the ml_iPod wiki (I am the admin) that SourceForge is really slow and the Php and Sql versions are old, in case you want to set up something like MediaWiki! You might want to try http://code.google.com/ , it has a built in Wiki and you can host files!
Just a suggestion
Keep up the good work
EDIT: I could even set one up, if you want, but I am not into coding at all!
Hi! Sorry for the delay, but I'm having lots of work this week and I've been unable to keep on with this...
@Walram: On the following days I'll try to build a kernel for you, wich should put all the lights on and makes the phone vibrate until you take the battery out Obviously just for testing, it shouldn't break anything, but I need to know if the originally-made-for-the-tornado vibrator and led drivers actually work on the tornado... Thanks!
@Frauhottelmann
Didn't know that google gave that service too! will look at it this weekend and post back when I have something done with this.. thanks for the feedback!
walram said:
I have a tornado (and vox and wings), so tell me what to test
Click to expand...
Click to collapse
Hi!
Ok, here's what I want you to try. If you haven't downloaded it yet, download the Linux Test Image:
http://rapidshare.com/files/93938763/test.zip.html
Then, download the kernel for the tornado:
http://rapidshare.com/files/96145010/kernel_tornado_driver.tar.gz.html
Dump the contents of the first file to the memory card, and then overwrite the file "zImage", with the one from the second link. Run haret, and hit "Run".
It should, at least, boot. If it doesn't, tell me where it gets frozen (could be that you only se some dots on the screen, whatever appears, just tell me )
If it boots, don't stop looking at the leds (charge/bluetooth leds mainly), they should, at least, flash -theorically they should stay on all the time-. It also should vibrate, at least for a quarter of second
I just need to know what it actually does!
Thanks!
So what about a dev-page? Then you don't need to upload it to Rapidshare and you can see the progress better!
Hi frauhottelmann,
I'm going to tell you the truth. I think it would be better if it's you who admins a site for this project than if I do, for various reasons:
1. I started all this thing, but I'm no owner of anything, by now I just hacked four things to make this phone boot a kernel, but no more.
2. I've seen your work at the ml_ipod sourceforge page, and think it's usable, clean, and nice, and I think that's exactly what we would need (even if it's a little slow just as you stated in your previous post). I could make the graphics for the web (I'm quite decent at photoshop), but I have never built a wiki, or a project anywhere else, and I don't know a sh** about it, so that would be another big thing to learn, and for now, I gotta learn more about the linux kernel, and that itself it's huge.
3. I don't think I can handle work, classes, building patches, kernels and bootstrap images and administrate a site, it feels like too much for me
Conclussion? I think it's better to let people do what does better, and I'm quite sure you'll do it better than I, so if you want, it's all yours
PS: In any case, we will need a name for the project, any suggestions?
What I have heard from the ml_iPod developers is that upload to SF is not a nice process either. I still think Google code is better, although it's not as customizable as SF.net. But we could also set up a page on Googlepages (pages.google.com) and then point to the Google code site with the Wiki and downloads!
I can offer my technical know-how (SPL, GPIOs, etc.)
Since I have little time you should ask me precise questions for which I can try to find the answers.
Sorry for the delay...
frauhottelmann said:
What I have heard from the ml_iPod developers is that upload to SF is not a nice process either. I still think Google code is better, although it's not as customizable as SF.net. But we could also set up a page on Googlepages (pages.google.com) and then point to the Google code site with the Wiki and downloads!
Click to expand...
Click to collapse
So we can start using google code, and stick with it if it goes well. We can always change the hosting if something goes wrong! About the wiki, the easiest thing is start with google code too, and simply link the xda wiki to it...
i can't code, but i can keep you company maybe
i am here if help is nedeed
But what name do we want to use?
Linux for Vox?
LinVox !
how does that sound ?
just kidding
waiting to get linux running on my vox....
But what name do we want to use?
Click to expand...
Click to collapse
Hooked on Vonix!
vonix sounds ok
can also try "Mobile TUX"
wow
this is an incredible news ! linux on the Vox !
I'd love to flash mine with a movibuntu distro =)
How do you guys feel about splitting the project up in several subprojects?
Like:
Kernel and driver work: TI OMAP HTC Vox board patch and perhaps drivers
Base system: minimal rootfs and toolkit to utilize all Vox functionality
Usability: GUI and (for instance) Android support
This would also enable us to share the base system & usability work with other 'linux on smartphone' and embedded projects.
I do have a suggestion for the base system:
www.emdebian.org
Very up to date build toolchain for arm (GCC 4.x toolchains) and you can have apt support on the base rom. This would allow access to a huge amount of packages that can be used with relatively little effort. Others I've checked out are the new mobile ubuntu (system requirements way to high), MontaVista (severe lack of proper documentation to get up to speed quickly), uClinux (uses ulibc instead of the faster full fledged one, in my opinion we'd better trade some storage for more speed) and some others I can't remember now...
PS. I've got internet at my new place and I've recovered my bricked wizard from the 'spare electronics bin', so finally I can spend some more time on this
Attached is a kernel source patch that fixes the EB13 camera video lag and "Sports" scene mode force-close. It's actually the same kernel bug that's responsible for both.
Also attached is an Odin/redbend-flashable, otherwise stock EB13 kernel with this patch applied. It's intended for anyone who wishes to further test the fix and who is familiar with Odin and/or redbend_ua. For others, I'd recommend waiting until one of the custom kernels integrates the patch or until Sprint releases an official update.
I'll update this post in the morning with a workup of the bug (done, see below), since it's a bit interesting/illustrative. And yes, it's very simple and very silly. One of those things that really never should've happened. Thanks to everyone in the solutions thread for providing clues that were instrumental in locating it.
Bug details:
Shortly after the release of EB13 folks reported lag when recording videos, particularly in low light. Although not obviously related at the time, folks also reported that switching to "Sports" scene mode results in a force-closed (and in my experience, renders the screen inoperable as well, sigh). Folks in the solutions thread also reported that (i) these problems are new to EB13, they weren't present in DK28; and (ii) replacing the user-space camera components (app, libraries, etc.) with DK28 versions did not resolve the problems, implying they were likely due to one or more kernel bugs.
Unfortunately we do not have the DK28 source code to compare EB13 against, but at least knowing that these problems weren't present in DK28 helps narrow down the possible bug locations quite dramatically. Furthermore, it's quite likely that this bug was introduced rather recently, as I imagine it would've been caught by internal testing had it been present in say, December.
So with that in mind, I sorted the kernel source files by modification time and started looking for the most recently-changed files that might be relevant to the camera driver. "include/linux/videodev2_samsung.h" was the first hit with a modification date of 2/8, and indeed it's used by the camera driver ("drivers/media/video/victory/ce147.c", itself last modified on 12/1). Again, we don't have DK28 sources for comparison, but fortunately header files typically don't change too significantly and a comparison (diff) against the DI18 version was rather easy to follow.
And yes, a snippet of code stood out right away as rather strange, especially given the cirumstances of the problem:
Code:
enum v4l2_iso_mode {
ISO_AUTO = 0,
ISO_50,
ISO_100,
ISO_200,
ISO_400,
ISO_800,
ISO_1600,
ISO_FIREWORKS, // Added since DI18.
ISO_SPORTS,
ISO_NIGHT,
ISO_MOVIE,
ISO_MAX,
};
For folks less-familiar with C, this code defines an enumerated type, basically a mapping of "descriptive labels" to numeric values; in this case: ISO_AUTO=0 ISO_50=1, ISO_100=2, etc. This enables kernel code to contain descriptive statements like "iso_mode = ISO_200;" instead of the more arbitrary "iso_mode = 3;".
Now, as the above comment (which I added, but the diff points it out) suggests, ISO_FIREWORKS is a new speed that was added to the middle of the enum since DI18. Seasoned C programmers will recognize that, this is often something that leads to trouble. To understand why, compare the "before" and "after" enum mappings:
Code:
Before: After:
ISO_AUTO: 0 ISO_AUTO: 0
ISO_50: 1 ISO_50: 1
ISO_100: 2 ISO_100: 2
ISO_200: 3 ISO_200: 3
ISO_400: 4 ISO_400: 4
ISO_800: 5 ISO_800: 5
ISO_1600: 6 ISO_1600: 6
ISO_SPORTS: 7 ISO_FIREWORKS: 7
ISO_NIGHT: 8 ISO_SPORTS: 8
ISO_MOVIE: 9 ISO_NIGHT: 9
ISO_MOVIE: 10
The addition of ISO_FIREWORDS to the middle of the enum shifts the mapping of any labels below it, in this case ISO_SPORTS, ISO_NIGHT, and ISO_MOVIE. This isn't fatal, but it does mean that all code that uses the enum needs to be recompiled to reflect the new mapping. Often, kernel header files contain data types that are exclusive to the kernel, so any relevant code gets recompiled as part of the process of compiling a kernel.
But as it turns out, the entries in this enum are used in exactly one location (on the Epic anyways) in the kernel: as a case in a switch statement in the camera driver that sets the ISO mode in a camera hardware register. This means, assuming these values are used at all, they must be provided by a user-space library. In other words, the enum mapping is an integral part of the driver API, and not something that can be altered willy-nilly.
So basically, on EB13 when the Camera app goes to record a movie, it sets mode ISO_MOVIE (9), which the kernel interprets as ISO_NIGHT and sends to the camera hardware. Presumably ISO_NIGHT biases picture quality over shutter speed, hence the blurry laggy video when recording. Similarly, ISO_NIGHT => 8 => ISO_SPORTS (which no one noticed), and ISO_SPORTS => 7 => ISO_FIREWORKS. Except ISO_FIREWORKS isn't implemented, so the driver call fails which results in the force close. Oops!
The fix is fairly simple, just remove ISO_FIREWORKS from the enum. This allows the kernel and the user-space libraries to agree on the mapping. And since ISO_FIREWORKS isn't even implemented in the kernel, no harm can possibly come from it.
Finally, as I stated earlier, this is a bug that never should've happened, for two reasons. First, it was introduced into the Epic kernel source tree after DK28. Now, keep in mind that DK28 was effectively a Froyo "release candidate", especially given that it was packaged up as an OTA update and accidentally pushed to some handsets. Any changes made to the kernel post-DK28 should be limited to strict bug fixes only. The addition of ISO_FIREWORKS to the enum is not part of any bug fix (indeed it introduces one), rather one would consider it a "new feature". But "new features" shouldn't creep into stable code trees. This suggests poor code management.
Second, this alteration would've been a non-issue had ISO_FIREWORKS been appended to the end of the enum, just before ISO_MAX (which, presumably just reports the numer of entries in the enum as opposed to describing a particular mode). This would've assiged ISO_FIREWORKS to an unused value, instead of remapping existing values. Adding ISO_FIREWORKS to the middle of the enum is a particularly short-sighted choice, as it immediately renders any code that uses it unnecessarilly incompatible with new kernels. Adding ISO_FIREWORKS to the end preserves backwards compatibility, for free, with absolutely no downsides--why not do that instead?
So, in short, the failure to properly consider both of these issues, as well as the neglect to notice the change, bespeaks of an incompetent moment on the part of Samsung. If the change really was made on 2/8, one can't really blame Sprint for failing to pick it up during last-minute testing. I'm not sure how much this particular bug was a factor in Sprint pulling the EB13 update, but it's pretty embarassing that it made it out there in the first place.
Mirror links (does not require forum login):
epic_camera_fix-EB13.diff
epic_camera_fix-EB13.tar
epic_stock-EB13.tar (for flashing back to the stock EB13 kernel)
Thank you! This will be in the ACS kernel team's kernel.
Excellent, patching up as we speak.
Sent from my SPH-D700 using XDA App
Just wanted to be 3rd
Sent from my SPH-D700 using Tapatalk
Cool, looks good.
Sent from my SPH-D700 using Tapatalk
patching myself too thx will be in Genocide Kernel 0.3a
THANKS! leave it up to xda to do a better job then Samsung lol
Sent from my SPH-D700 using XDA App
Sweet,
tested working perfect. the LSD trails in video are gone and no FC in sports mode. TY so much.
fix worked great! i just released genocide 0.3a with this patch included! thanks again!
Gotta love 1 line fixes
Would like to try this but only have mac os so odin...
Awesome, thanks man!
Sent from my SPH-D700 using XDA App
Noob question.
Do you put this in PDA? Also no need for PIT or modem file right?
Via TapaTalk on Nook Tablet
-Edit-
Okay, used Odin, put patch in PDA with nothing else set. Worked perfectly! Thanks to all!
You sir a genius....thx for this fix!!!
What is sports mode? I can't find it.
Silent25r said:
What is sports mode? I can't find it.
Click to expand...
Click to collapse
Still camera, settings (gear button)>Scene Mode> Sports Before the fix it's an automatic FC
Can't wait to hear the details behind the bug.
Sent from my SPH-D700 using XDA App
This patched worked perfectly on the genocide kernal!! Thanks For Your Hard Work!!
Now Just Waiting For Bonsai!!
The geniuses at XDA strike again! Brilliant! Thanks!
MoCoTerp said:
Noob question.
Do you put this in PDA? Also no need for PIT or modem file right?
Via TapaTalk on Nook Tablet
Click to expand...
Click to collapse
Help please? I've flashed lots of roms but never a kernal like this. i'd like to stay with the stock ROM. Can't find anything on a search. Can someone either post a link or instructions.
[size=+3]
NEW VERSION
Ainol Novo 8 Adv 2.3.4 Rooted UK Rom Version 2.0 Click Me!!
Ainol Novo 8 Adv 2.3.4 Rooted UK Rom Version 2.0 Click Me!!
Ainol Novo 8 Adv 2.3.4 Rooted UK Rom Version 2.0 Click Me!![/size]
The Ainol Novo 8 is a great little tablet but has been hampered by some early quality issues and about 4 or 5 firmware revisions that have all been good at something but not everything.
Recently a 2.3.4 beta Rom appeared on the Chinese speaking boards and was a major improvement over the 2.2 releases however as always they were in Chinese as a first language and contained stuff that was no use to us English speaking types. So I decided it was time to apply a bit of magic and make my own Rom. Links at the bottom of the post. This is a direct result of my playing about with the beta firmware then bringing it all together.
Link to my blog post Nebular Nerd @ Blogspot
From the readme.txt
-----------------------------------------------------
Ainol Novo 8 Advanced 2.3.4 PreRooted English Rom
Hacked together by Nebular Nerd (Nov 6th 2011)
(If it's not broke, make it better)
aka thedaybeforetommorow (MP4Nations forums)
aka Oberth (XDA-Developer forums)
WWW: http://nebularnerd.blogspot.com
-----------------------------------------------------
About This Firmware:
--------------------
After much frustration having to de-Chinese every firmware for this amazing little tablet I set about making an English one to save time and to learn a bit more about Android, while doing so I also added in the main Google apps that everyone wants but always has trouble getting to behave. Using the current 2.3.4 beta as a base I removed, replaced and added various things to give us a decent firmware that will make you proud to show off your tablet with the unfortunate brand name. (Hands up all those who have had a schoolboy snicker when telling someone who makes it)
While I take credit for the putting everything together in one easy to use package the real credit should goto all those people I sourced the component parts from. Enjoy the firmware
Changelog:
----------
8/11/2011:
Tidied and formatted readme.txt.
6/11/2011:
Minor update to correct bug in build.prop preventing Chianfire and Tegra games from working.
5/11/2011:
1st Release.
Sources:
--------
http://tinyurl.com/63pnbl6 The base for my rom was this prerooted one. (Translated)
http://tinyurl.com/64xhw3y I used the Browser and Google Music from this one. (Translated)
http://tinyurl.com/29c6jlx The rom I currently use on my HD2 which I lifted most of the Google stuff from.
http://tinyurl.com/6y57c4s The tweaks used for the Market.
Other various sources for stuff about some of the other little tweaks.
Installation:
-------------
Flashing this is a breeze, simply copy the contents of the zip to your SD Card, insert into your Novo 8 and boot into Recovery with Power & Vol+.
Once booted perform the 3 wipes and then install the update and reboot. That's it, no need to install the AC3/DTS license or add Google apps.
If you spot the error about the factory_*blahblahblah*.aml file missing when booting into recovery mode just ignore it. I dumped the automated stuff as it bricked my unit the first time round when flashing the stock beta and I had to do a recovery with the original firmware release. All the automated bit really does is perform the 3 wipes and perform the install so why risk it when it takes only a few seconds to do.
When first booting the homescreen will go black/blank for about a minute. Don't panic this is quite normal it's just everything unpacking and setting up. Set up your wifi, add your Google account and off you go.
Features:
---------
- AC3/DTS Hardware Decoder works.
- Fast and Smooth 160dpi rom with build.prop tweaks to improve battery life and speed things up.
- 3G Modem support is present and has been confirmed working with these dongles . . .
Huawei E160 3G USB Dongle (ompudsman @ MP4Nations)
Huawei E1750 3G USB Dongle with Virgin UK sim. (GFZ @ XDA)
- Full English Rom set to UK region, no hidden Chinese menus to pop out at you. All Chinese only apps removed or replaced with english versions.
- Latest Market 3.3.11 with heavily modified build.prop to show as many apps as possible. This does actually show and install a far wider range of apps than before.
- Uses the free version of LauncherPro because it does seem the best for this Tablet, the Chinese firmwares seemed to have hard coded Chinese in the LauncherProPlus.apk The market will allow you to purchase the Plus Unlocker if you want those features.
- Preloaded with Google Browser, Gmail, Maps, Streetview, YouTube, Google Music, Latitude, Google Search, Calendar and Car Home.
- Google accounts will sync Contacts, Mail and Calendars correctly.
- YouTube plays HQ videos just fine without stutter or lag. (Assuming you have a good wifi signal)
- The stock video player plays most MPG, MP4, MKV files with AAC, MP3, AC3 audio. Plays 1080p quite happily as well if the storage device can keep up.
If you need wider format support but still with hardware decoding where possible get MX Video Player and the ARMv7 Codecs from the market.
- Most of the Games and Apps I have tried while testing work fine. Get Chainfire3D and buy the Pro key to enjoy some of the nice Tegra Games. Check my blog for compatibility of Tegra games.
- Wifi seems better under the new firmware.
Bugs: (Most of these have been documented as an issue with the base firmware)
-----
- Tablet likes to wake itself up now and then for no real reason. (Possible data connections causing it to wake)
- Sometimes the Power button does not work so you can't turn off the screen or power off. Install Quick Reboot off the market or hit the reset button.
- If the Screen is off and the Power button is not behaving another key will turn it on.
- Sometimes the Power Off dialog appears for no reason. Oddly not when in full screen games so far as I've noticed.
- Your Novo may disappear off the Market site for a while or completely. Mine went and then came back about a day later,
this is down to the modified build.prop. You can still download apps directly through the Market app on the Novo regardless.
- Some of the best apps are still not available in the market, Dolphin Browser HD, Facebook and Friendcaster to name a few. This is down to Google Market and not much seems to beat this last hurdle.
- Possible others (Let me know by posting on my blog or threads)
Disclaimer:
-----------
As with any custom firmware there is a risk of things going wrong so if it bricks your unit try a recovery image from Ainol and start again, if you are of a nervous disposition or the type of person who sues for a hobby please do not attempt to install this. The rom works fine on my unit and others have tried without issue, however mileage does seem to vary with this tablet.
----------------------------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(screenshot app not included)
Links to the firmware (if you want to mirror please let me know so I can add links here)
Novo 8 2.3.4a Firmware UK Edition (nebularnerd.co.uk, fixed March 2021)
Thank you!
Hi Oberth,
Thank you so very much for the hard work and effort to put something together for this fantastic tablet! We have been hoping to see some english rom's being put together for some time but the fact that this is Android 2.3.4 with all the tweaks and best bits of previous rom's is excellent!!
Will be flashing your rom shortly and report back...
update: flashed and so far so good!
- Huawei E1750 3G dongle tested with Virgin UK Sim and all working.
Also will be uploading you rom to our website which may be found in the download section of the Ainol Novo 8 webpage.
(unable to post a link yet as need more posts)
Kind Regards
gadgetfreakz.co.uk
Thanks for the feedback
I actually bought my tablet from you guys through your ebay shop under the user id thedaybeforetomorrow was most pleased by the service.
Thanks for the offer to mirror and I hope the rom performs as it should, as not everyone can/will download from rapidshare I would like to add the links for your Novo 8 page to my first post here, my mp4nation thread and my blog.
Over at MP4 I have had some feedback regarding the market, while fully functional some have complained of the speed (mainly to do with the markets new design rather than tablet performance) so I am considering for the next release maybe offering both the older 2.xx style market and new 3.x market as separate firmware downloads so people can choose. Both the latest version I have used and the older one seem to see the same amount of apps visible so it's mainly a personal preference.
Just seen your test with the 3G Dongle, going to update here there and everywhere
Oberth said:
I actually bought my tablet from you guys through your ebay shop under the user id thedaybeforetomorrow was most pleased by the service.
Thanks for the offer to mirror and I hope the rom performs as it should, as not everyone can/will download from rapidshare I would like to add the links for your Novo 8 page to my first post here, my mp4nation thread and my blog.
Over at MP4 I have had some feedback regarding the market, while fully functional some have complained of the speed (mainly to do with the markets new design rather than tablet performance) so I am considering for the next release maybe offering both the older 2.xx style market and new 3.x market as separate firmware downloads so people can choose. Both the latest version I have used and the older one seem to see the same amount of apps visible so it's mainly a personal preference.
Just seen your test with the 3G Dongle, going to update here there and everywhere
Click to expand...
Click to collapse
wow, small world!
thank you for your custom and delighted to hear you are pleased with the service
will be testing further over the next few days, for some reason we did notice that the initial firmware form Ainol played 1080p files flawlessly then slowly playback became worse over following updates although other features/fixes had been implemented.
all mentioned above seem to be as you stated regarding the initial power up and blank screen. can't say we experienced the power button problem yet, works as it should.
the new market is indeed sluggish as with other tablets, a quick search for skype didn't show the main application as most likely with some others that you have mentioned. apart from the sluggish launch, the new market design is not so bad, personally prefer it now being used to it.
Ainol did advise an official firmware was due soon, maybe a mix of that and the firmware's you have worked with will give us an even greater improvement.
loving the honeycomb boot animation!
keep up the great work, will have the firmware link etc added shortly.
The playback issues in the later firmwares linked to the AC3/DTS license not being installed or disabled entirely so playback did get worse.
Can I ask you to re-download the firmware in the first post. I tidied up the readme.txt for readability. nothing else is changed.
Oberth said:
The playback issues in the later firmwares linked to the AC3/DTS license not being installed or disabled entirely so playback did get worse.
Can I ask you to re-download the firmware in the first post. I tidied up the readme.txt for readability. nothing else is changed.
Click to expand...
Click to collapse
sure no problem at all, we have uploaded the firmware to our novo 8 pages download section and provided link to the firmware and to this page at xda.
will download new file and replace the one we have on our server.
thanks again
Thanks for that I have added your page to the links section where ever this is posted and edited my blog to mention where I bought it from.
Can I ask if you could change the name from Oberth to Nebular Nerd on your page, just matches up with the blog then. My user name from here was from years back and I wish you could change it. Part of why I edited the readme was to aka the names
Oberth said:
Thanks for that I have added your page to the links section where ever this is posted and edited my blog to mention where I bought it from.
Can I ask if you could change the name from Oberth to Nebular Nerd on your page, just matches up with the blog then. My user name from here was from years back and I wish you could change it. Part of why I edited the readme was to aka the names
Click to expand...
Click to collapse
will do
may be in touch soon regarding some ideas we have that may be of interest.
thanks again
Man, this is great!
Thank´s a lot!
Now I´m happy with my tablet.
Hello from Spain
First of all, congratulations on your work with the tablet Ainola.
I wanted to ask if you know when it will be available in Spanish.
Thanks for everything.
kinterinho said:
Hello from Spain
First of all, congratulations on your work with the tablet Ainola.
I wanted to ask if you know when it will be available in Spanish.
Thanks for everything.
Click to expand...
Click to collapse
I just checked and Spanish language is not included, maybe something for the next release
Languages included are: English (Australia / Canada / New Zealand / Singapore / UK / United States) & Chinese.
Thanks, I'll try to see how it goes anyway.
But if you can include it in the next version, would be welcome here in Spain.
kinterinho said:
Thanks, I'll try to see how it goes anyway.
But if you can include it in the next version, would be welcome here in Spain.
Click to expand...
Click to collapse
That would be down to Oberth aka Nebula Nerd but don't believe it would be that hard to do, i'm sure he will let us know
Additional Languages
Hi kinterinho,
I shall have a look into adding additional languages into the firmware and see what that requires. This beta was released with only Chinese and English language files built in but I may be able to borrow some from another rom.
The only thing that might present a problem is if LauncherPro refuses to change all it's options to Spanish in the same way the default Chinese one would not become fully English when you changed the language. I shall have to experiment and see
Cheers for the update, having a few issues.
Iplayer app now apears to suck goats since using this ??
any ideas ?
rezza.dh said:
Cheers for the update, having a few issues.
Iplayer app now apears to suck goats since using this ??
any ideas ?
Click to expand...
Click to collapse
Hi, I think you will find the BBC iPlayer app has always had issues.
Playback should be fine via the browser, this firmware plays iPlayer via stock browser although previous firmware required dolphin browser hd.
Oberth said:
Hi kinterinho,
I shall have a look into adding additional languages into the firmware and see what that requires. This beta was released with only Chinese and English language files built in but I may be able to borrow some from another rom.
The only thing that might present a problem is if LauncherPro refuses to change all it's options to Spanish in the same way the default Chinese one would not become fully English when you changed the language. I shall have to experiment and see
Click to expand...
Click to collapse
I appreciate you try it. In Spain would do well to include also the Spanish language.
I read on the post to see if there are any changes.
iPlayer is indeed pretty poor.
Yep confirming GFZ's post, it will play with the stock browser set to mobile but quality is pretty poor. I remember it running better on one the original stock roms. It could be one of a few things.
- Bug in the firmware with flash, although Youtube works through the various browsers ok. You can't use the Youtube app for comparison as it's not flash driven.
- Could be a VM Heap issue with it taking up to much space (need to play with that and see)
- Could be the higher dpi on top of the higher res causing the poorly coded app lots of effort in the upscale, dropping to the original 192dpi might cure it at the expense of fuzzy text and icons, again I need to test, not sure if dpi switchers play nice with this rom so you could at least hop between them for different tasks.
- I might try embedding it in the rom as well, The Youtube app hated being added to the tablet post flashing and performance was poor but ran just fine after being flashed in.
The problem with iPlayer for Android was that it was released only after a lot of complaints from the community at large about them only supporting the iThings. BBC were not really wanting to make it but cobbled something together just to shut people up.
Quick edit: Hit the settings button and drop the quality to low in iPlayer seems to play the same as in Browser. Not ideal I know, looking at it more closely it seems to be a buffering issue as you get a few smooth seconds and then it all grinds to a halt.
Multilanguage support
Hi kinterinho
I have been looking into and reading up on how Android handles multiple languages and it looks like it not something easy to do as it's not a case of adding files but adding stuff into the files and given the differences between roms especially 2.2 and 2.3 ones I imagine a cut'n'paste job wont do it.
However I have the beginnings of an idea, it needs some work combined with a recent opportunity that has come my way so I can't promise anything but watch this space.
Thanks you!
I created this thread because I found interesting thing about our devices. Many people complain about work of GPS in i9001. Slow fix, and disconnecting are only part of problems. Yesterday i was reading about navigation and found a solution. All Qualcomm Snapdragon S2(so our MSM8255T too) series chips support both GPS and GLONASS. GLONASS is russian system of satellite navigation. In GPS system are 27 satellites and in GLONASS we have extra 24. It look that our devices uses only half of power.
More here:
http://www.phonearena.com/news/All-...vices-supporting-both-GPS-and-GLONASS_id24830
http://en.wikipedia.org/wiki/GLONASS
EDIT[04.12.2012]:
I reactivate this thread, I hope any real developer will port it. If you have any idea post it here, or just search this thread and look any of this *zip make it work even partially.
I solved the problem with slow fix...
Before starting the navigation, i use gpsfix with mobile data turned on. Effect is instant GPS fix...
Karls0 said:
I created this thread because I found interesting thing about our devices. Many people complain about work of GPS in i9001. Slow fix, and disconnecting are only part of problems. Yesterday i was reading about navigation and found a solution. All Qualcomm Snapdragon S2(so our MSM8255T too) series chips support both GPS and GLONASS. GLONASS is russian system of satellite navigation. In GPS system are 27 satellites and in GLONASS we have extra 24. It look that our devices uses only half of power.
More here:
http://www.phonearena.com/news/All-...vices-supporting-both-GPS-and-GLONASS_id24830
http://en.wikipedia.org/wiki/GLONASS
I want to start a discussion - is it possible to port support of GLONASS to our phones (e.g. from xperias from 2011)?
Click to expand...
Click to collapse
there is no need to port glonass
it is already implemented in our phones
you can check if your gps is using these satellites by using gps test
every satellite has an own specific number
gps (usa satellites) are using the numbers 1 to 31 i think and
glonass (russia satellites) are using the numbers 65-88
glonass satellites are only used when gps has a bad signal e.g. in buildings
Ok, but extra 24 satellites will give us much better accuracy. I don't have problem with fix but sometimes when it's cloudy accuracy is about 15m-20m, more satellites will help with this problem.
We don't know how much it will help, but we have to try if we want to be sure. Now accuracy is good for car navigation but in off-road it's a bit to weak.
Edit:
Blumdum said:
gps (usa satellites) are using the numbers 1 to 31 i think and
glonass (russia satellites) are using the numbers 65-88
Click to expand...
Click to collapse
I tested in "GPS test" and numbers was between 1 and 31, so only GPS range.
you are wrong, here is a proof:
Our config:
NTP_SERVER=europe.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
Click to expand...
Click to collapse
SGSIII config:
TP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://gllto.glpals.com/4day/glo/v2/latest/lto2.dat
XTRA_SERVER_2=http://gllto.glpals.com/4day/glo/v2/latest/lto2.dat
XTRA_SERVER_3=http://gllto.glpals.com/4day/glo/v2/latest/lto2.dat
SUPL_HOST=supl.google.com
SUPL_PORT=7276
Click to expand...
Click to collapse
In xtra.bin file are only GPS data, to use both systems phone need lto2.dat where are informations about position of GPS and GLONASS satellites.
I found that SGSII too support Glonass:
http://androidandme.com/2011/12/news/qualcomm-enables-dual-core-location-on-snapdragon-phones/
It look like our phones doesn't have enabled glonass by default but it is possible to do it.
http://forum.xda-developers.com/showthread.php?t=1436776 - it's for WP7, do you think it is possible to do something similar for our phones?
That's great. thanks for share.
Just use this http://forum.xda-developers.com/showthread.php?t=1685726
If I remember correctly our exact processor doesn't support GLONASS. Its never, refreshed version (don't remember numbers) does and it is even possible to switch hardware beacouse it has the same amount of pins. But you'll propably break your phone by doing so.
I also read today about GLONASS and supporting processors and our model is on the list. So I'm a bit confused.
We have hardware support for glonass, but I tested this theory that our phone support it in software. Look at the screenshoot - only gps satelites. So capability of our navigation is reduced to half by software :/ We need good developer to port it from sony phones or some galaxy devices (SII SIII, Note)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well. We allready have a fast gps-lock fix somewhere in this development section (maintained by broodplank, if i remember ot right). He alleady had a super easy way to get a faster gps lock (in about 5 secondes or something like that) i know BroodRom rc5 rev 2 has this gps fix pre-installed. Try the rom and see how fast gps is.
Sent from my SGS+ using the xda app
Fix is enought fast for me, i rather think about better accuracy like on SGSII or SGSIII. Even Xperia arc S have GLONASS support :/ samsung is really retarded with software,
People. We cant get everything at once. We need good kerneldevelopers to get 3.x kernel.
Sent from my GT-I9001 using xda app-developers app
XeLLaR* said:
People. We cant get everything at once. We need good kerneldevelopers to get 3.x kernel
Click to expand...
Click to collapse
DoomsDay explain why this kernel is not needed, it will not change to much. But please stop off top.
Sony Xperia Arc S have this same chipset and get glonass support with .62 update. Here is it:
http://forum.xda-developers.com/showthread.php?t=1408142 - i will try to look at this, but I'm not a developer, just a hobbyist, so without your help don't expect to much :/
interesting approach
Karls0 said:
DoomsDay explain why this kernel is not needed, it will not change to much. But please stop off top.
Sony Xperia Arc S have this same chipset and get glonass support with .62 update. Here is it:
http://forum.xda-developers.com/showthread.php?t=1408142 - i will try to look at this, but I'm not a developer, just a hobbyist, so without your help don't expect to much :/
Click to expand...
Click to collapse
First of all thanks for gathering the huge amount of information and linking them. I think that someone of the devs/cookers will grab the information and use them earlier or later. Keep on searching for news around "Glasnost" I would like to have a more accurate GPS - not the speed of the fix is of importance and it is not the main intent in this thread...
Wish you (and us) succees... :good:
Rhonin
XeLLaR* said:
People. We cant get everything at once. We need good kerneldevelopers to get 3.x kernel.
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
i think XeLLaR means that we need all the good developers to get the kernel working. That is just the most important thing right now.
and i never had any problems with accuracy. the gps always brought me to the destination
I wouldn't mind if you work on it you self, but i personally think that the developers l need to focus on the kernel right now.
Sent from my GT-I9001 using xda app-developers app
But not everyone uses gps to navigation. Others use it to tracklogging as well.
I use it for geocaching so good accuracy is priority. I'm working on port this from Xperia Arc S, hope I will release first .zip soon. I'm not sure it will worke but have some ideas
Edit:
OK first test: I added some libraries, let's see what changed. I recommend to test it only on CM9-based roms. I'm almost sure it will not work on GB
Instruction(remember to make backup):
1. Reboot to recovery (CWM or TWRP)
2. Wipe cache and dalvik (full wipe not needed)
3. Install zip
4. Wipe cach and dalvik
5. Fix Permissions
6. Test
To test use one of this apps:
1. https://play.google.com/store/apps/details?id=com.chartcross.gpstest&feature=search_result
2. https://play.google.com/store/apps/details?id=com.gpsdatamonitor&feature=search_result
Check PRN's number of satellites. GPS numbers are 1-32 and 65-92 are for Glonass. If you can see these higher numbers it means it works!
WARNING! I'm not responsible for any damages or bricked phone
Karls0 said:
DoomsDay explain why this kernel is not needed, it will not change to much. But please stop off top.
Sony Xperia Arc S have this same chipset and get glonass support with .62 update. Here is it:
http://forum.xda-developers.com/showthread.php?t=1408142 - i will try to look at this, but I'm not a developer, just a hobbyist, so without your help don't expect to much :/
Click to expand...
Click to collapse
No and Yes. We can get a Port of Jellybean with 2.x Kernel but it wont be able to have Butter inside of it. Thats because the 2.x Kernel doesnt Support the Kind of V-Sync that Jellybean needs for V-Sync.
3.x Kernel isnt just Usefull for Jellybean. It will help developers to Port other things to our device in the Future. For example Newer android versions and Mods like BLN wich is a pain in the ass now.
Sent from my GT-I9001 using xda app-developers app
I don't have CM9 so I won't try it. Maybe try to change the forum thread name to encourage users to test it.
It can be any CM9-based rom, e.g. Paranoidandroid, BioHazard, Ehndroix. I'm not sure about AOKP based but if libraries structure is similar it can work. The most important is that it has to be ICS rom.
This thread has been created
for
Questions & Answers/Troubleshooting
Specific to
Planet Computer's
Cosmo Communicator
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters............
To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.If you have ROM-related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!Supporters: If you want to be put on or off the list, just make a request here in the thread!Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
FAQs for Device Thread link
Index for Device Thread Link
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here.
Cosmo Bug reporting
Muti-boot and Linux
Specs, Offical Site
https://store.planetcom.co.uk/products/cosmo-communicator
How to page
http://support.planetcom.co.uk/index.php/Linux_for_Cosmo
https://support.planetcom.co.uk/index.php/Latest_Cosmo_Firmware
XDA
https://www.xda-developers.com/cosmo-communicator-clamshell-android-pie-dual-boot-linux/
Features
Keyboard: Mechanical full keyboard
Backlit: Individually illuminated keys, with brightness adjustment
Fingerprint Sensor: Yes, sub-glass sensor
[email protected]
Your perk has shipped
-Nov 26, 2019, 6:04 AM
first impressions and rooting
Hi,
hope this thread is the right place - I'm new to posting on xda developers (but been reading here sometimes for a long time).
I received my Cosmo on tuesday (2019-11-26).
Overall I'm happy with the device. The keyboard is good and I can actually touch type with it - obviously not as fast as on a full sized one. But Sometimes it misses characters, expecially the space bar.
The german layout is a bit awkward for umlauts. To Type "ä" you have to press "Fn+a", for "ü", "Fn+u" and so on. There is only one Fn key on the left side so fluid typing of especially "ü" and "ß" is difficult.
Software on the cover display feels like an early beta. Very slow and e.g. music controls don't work with all music players - but it has it's value for checking the time or answering calls (and seeing who's calling beforehand).
Battery life is pretty bad but surprisingly unaffected by usage.
... well, it's a low volume device so I'm ok with the downside. And I hope some will be fixed.
Planet computers promised to release officially rooted images and linux support etc.... it's not there yet.
But rooting was pretty straight forward:
activate "OEM unlocking" in developer settings
install magic manager
adb reboot bootloader
fastboot flashing unlock
reboot to bootloader again (not sure if necessary)
fastboot flash boot boot-magisk.img
(most people seem to use SP Flashtool, but it worked for me with fastboot which is open source)
I got the boot-magisk.img from here:
https://www.oesf.org/forum/index.php?s=&showtopic=35879&view=findpost&p=292918
https://mega.nz/#!U8sFVACI!J-TS3q11Hak-zWt1_nyTyv4m87GkV1YIVDipez05BvE
When planet releases debian images I will try them out.
If you have any questions feel happy to ask.
edit:
the process does a factory reset. So back up your data!
Great
I was a little concerned when I got it yesterday.
Before powering on the first time I inserted a micro sd card.
Powered it on and it just said starting up for 39 mins
Ended up pulling the sd card out, now it works great.
Not sure what's up with that.
deadman96385 is supposedly working on TWRP and lineage os
Sent from my Cosmo_Communicator using XDA Labs
What filesystem do you have on the sd card?
The Android version is missing some filesystem drivers e.g. exfat and ntfs.
I have 64GB sd card formatted with vfat(32) and it works withoud any problems.
kineyDE said:
What filesystem do you have on the sd card?
The Android version is missing some filesystem drivers e.g. exfat and ntfs.
I have 64GB sd card formatted with vfat(32) and it works withoud any problems.
Click to expand...
Click to collapse
Not sure it was likely exfat.
Sent from my Cosmo_Communicator using XDA Labs
Still waiting for mine in the UK
Muti-boot and Linux Cosmo support update
From email
Muti-boot and Linux Cosmo support update
In this update we would like to discuss plans regarding Linux support on the Cosmo Communicator.
With the Gemini PDA, Planet offered experienced users the ability to install Linux on the device, by connecting it to a desktop or laptop computer and flashing the device manually.
With the Cosmo Communicator we want to improve the user experience when installing a custom OS, such as Linux. To do that we upgraded two key components, the LK and the recovery mode.
The updated recovery mode can be used to partition the storage space of the Cosmo Communicator - see the option "Change the partition table of your COSMO" in the picture below.
This will allow the user to reserve space for the Linux operating system. As you can see in the picture below, there are currently 5 options:
1. Reserve all space for Android
2. Reserve 90GB for Android and 30GB for Linux
3. Reserve 60GB for Android and 60GB for Linux
4. Reserve 30GB for Android and 90 GB for Linux
5. Reserve all space for Linux
Once the storage for Linux has been reserved, you can install a custom OS on your Cosmo, by choosing the related option as in the picture.
This option will scan the microSD card for compatible installers and will present you with a menu showing the available installers as in the picture below.
Whenever new or updated custom operating systems will be available for the Cosmo, you will be able to download them into a micro SD card and install it in your device.
At the moment we have initial support for the following:
1. TWRP (Team Win Recovery Project)
2. Debian using KDE/Plasma
3. Debian using LXQT
4. Rooted Android
Once you select a custom OS you have to select where to install its boot firmware as shown below.
There will be 3 extra boot partitions that can host custom boot firmware.
Once you select the boot partition, the custom OS will be installed on your Cosmo Communicator. A boot menu will then appear when you turn ON the device, allowing you to choose what to start as in the following picture. The boot menu is integrated in the modified LK firmware.
Using this method you will be able to install a custom OS such as Linux on your device without the need for a laptop or a desktop computer. All you need to do is to download the installer in a micro SD card and use the recovery mode to start the installation.
Finally, a big thank you to our open source community (in particular to Sean, Adam and Nikita) which is working hard to get other operating systems supported on the Cosmo. In the following screenshot you can get a preview on what the community is working at the moment. We will provide a detailed Linux status update in the coming weeks. Stay tuned!
More from us this still this week. There will be another update later this week updating you on the over the air firmware update and Cosmo shipping.
Best regards,
Team Cosmo
Click to expand...
Click to collapse
First Cosmo Firmware update - this week!
from email
This week, Planet will release the first Cosmo firmware update.
The latest Cosmo firmware includes new features and solves a number firmware issues reported by users:
1. New settings: switch OFF cover display on power down
This feature helps saving battery when Cosmo Communicator is powered down by switching OFF the cover display. When powered down in this way, you will only be able to switch on your Cosmo using the Esc key and charge your Cosmo using the left hand side USB-C port. We are looking at further power saving firmware possibilities
2. Fix for power charging indicator being on while the keyboard backlight is on.
3. The Duraspeed and Background Power Saving settings status is now OFF by default. This fixes the operation of many applications which were reported to be closing in the background when Duraspeed is ON. Some services were being closed down after some time of inactivity.
4. The eSIM chip status is now fixed after Cosmo restart, so eSIM selection is preserved (instead of switching to SIM lost 2)
5. Fix for Reject ringing call during another call from cover display
6. Fix for sending SMS reject call when two calls exist
7. Fix for Switch calls and merge calls from cover display
8. The Cover Display will now support the advertised landscape mode.
9. The Cover display will also support two font sizes for notification text.
10. Fix for icon sensitivity on top row of icons on the cover display
11. Optimisation for Contact list update on cover display
12. Some stability fixes for cover display
Cosmo Support Web Site
We have also started Cosmo support pages on support.planetcom.co.uk.
We will be updating these pages with more content in due course.
Click to expand...
Click to collapse
Cosmo Bug reporting
Cosmo Bug reporting
If you find an issue using your Cosmo Communicator you can report it using the
Cosmo trouble reporting board.
https://app.smartsheet.com/b/form/cc92fc88ec4e469d8923c419ad9321b2
cover display firmware update error
Hello All,
Just received my communicator and during my cover firmware update there was an interruption when I attached the charger to the device. Received flashing error message then tried recommended steps on support site to no avail. Does anyone know where I can get the firmware for a manual flash? My cover display is now not working and won't communicate with the device. Any help would be greatly appreciated.
Disregard. Apparently it can take up to 10 times for the flash to actually work.
new recovery
Does anyone have an idea when they are going to update the recovery so we can partition the drive for dual boot?
Anyone know how to make the Esc key behave normally in Android? I never had issues with using the Hacker's Keyboard escape key in Termux, but on my Cosmo pressing the escape key seems to work like Android's back button, which minimizes Termux. I just want to use it like a normal escape key. I currently have vim set to use tilde to go to command mode, but that's a janky solution for a number of reasons and it means that I have to use that setup on any other box I'm accessing a given remote server from. I've looked in Settings->Cosmo Settings and in the Planet Keyboard app, and didn't see it either place. Any help would be much appreciated.
Hi kineyDE,
Do you know which music player apps work with the music controls on the cover display front screen? I can't seem to get the cover display to respond to any of my inputs for any music player I have installed (music, FM, or video app).
VWrestle97
just installed a googlecam port. pictures are acceptable.. not as good as my old iphone 8plus, but good enough
this needed it's own thread:
https://forum.xda-developers.com/android/help/cosmo-communicator-to-post-t4032525
"I have a Cosmo Communicator that has been packed backed into it's box. I feel there are glaring security holes outlined in this article by Ninji:
https://wuffs.org/blog/pulling-apart...emfota-updater
With that said, I have not seen much discussion about the Cosmo Communicator here on XDA. I currently have a useless Cosmo because there is currently no Sailfish available for it, and it doesn't look like it will happen anytime soon. If there is a developer here that would like to work on it, I would be willing to loan out my device for that purpose.
Is there anyone else here who has a Cosmo?"
If a moderator want's to delete one or the other or let the separate one exist, i'm not worried. I just want to get this message out to the community.
masterhaides said:
https://forum.xda-developers.com/android/help/cosmo-communicator-to-post-t4032525
"I have a Cosmo Communicator that has been packed backed into it's box. I feel there are glaring security holes outlined in this article by Ninji:
https://wuffs.org/blog/pulling-apart...emfota-updater
With that said, I have not seen much discussion about the Cosmo Communicator here on XDA. I currently have a useless Cosmo because there is currently no Sailfish available for it, and it doesn't look like it will happen anytime soon. If there is a developer here that would like to work on it, I would be willing to loan out my device for that purpose.
Is there anyone else here who has a Cosmo?"
If a moderator want's to delete one or the other or let the separate one exist, i'm not worried. I just want to get this message out to the community.
Click to expand...
Click to collapse
Hi as stated by Ninji disabling the updater should secure the device (unless already compromised).
Code:
adb shell pm disable-user --user 0 com.dtinfo.tools
And once there is an update fingers crossed that there will be no new backdoor and you can turn it on again.
Code:
adb shell pm enable com.dtinfo.tools
So far I am very happy with my cosmo, but I am missing working volume buttons when it is closed.
lobertDE said:
Hi as stated by Ninji disabling the updater should secure the device (unless already compromised).
Code:
adb shell pm disable-user --user 0 com.dtinfo.tools
And once there is an update fingers crossed that there will be no new backdoor and you can turn it on again.
Code:
adb shell pm enable com.dtinfo.tools
So far I am very happy with my cosmo, but I am missing working volume buttons when it is closed.
Click to expand...
Click to collapse
As stated by Ninji in the article:
"Disabling the SystemFota package should stop the device from communicating with Digitime and running the worker, but the backdoor service baked into Android is still there, which allows any app to execute a variety of privileged actions. I assembled a proof-of-concept with it which was able to dump the Android accounts database (including auth tokens) without using Android permissions or requiring user input, from a standard app at API level 28."
You should read the ENTIRE article before commenting.
https://wuffs.org/blog/pulling-apart-the-cosmos-systemfota-updater
A software bug or hardware issue?
The power indicator shows charging while not connected to the charger. Don't know its a software bug or hardware issue?
Battery drains very fast even not using.