Ok, I decided that we need to collect the different ROMs made by the DEVs and sort them into 1 place.
What I like to do here is to try to explain the different ROMs Kit Kat and Lollipop by Malaysk, ###8310 and Booroondook.
And while we now know that MCU's need to stay via KLD, KLD2, KLD6 etc, you can upgrade within those parameters with only changing factory settings (KLD6-V2.83 to KLD6-V2.97 is ok)
I have played with these roms and follow an certain rule.. Before you go from Factory to a custom rom, take pictures of settings and factory settings.
Don't update unless you are sure you know how to revert back. Know what buttons to push. Know what screen resolution your unit is! All those minor points.
All the roms we are talking about look like a filename as "update.img". 4.4.4 and 5.1.1 all for MTCB and MTCC are called out this way. I do believe MTCD is something different (dupdate.img ???)
MCU for MTCB and MTCC are "mcu.img".. and are found on the file servers as KLD?-V2.?? .. sub your version (others are available)
The fileserver can be found under typos1 name on most posts. I will link it soon.
I would suggest you read his very informative wiki as well.
Malaysk (MTCB 4.4.4 and 5.1.1) is probably the most popular ROM here. He and like the other DEVs make the ROMs to their liking's. They will on occasion add suggestions to the ROM image if they think it is beneficial.
Malaysk and ###8310 (MTCB to MTCC fake out via xPosed does a reboot once to complete loading) will have 2 files to chose from which are for resolutions. 800x480 and 1024x600. Choosing the wrong one will make the your display look awkward. (reason to know how to get back into recovery if you make this mistake)
Booroondook has a setup that creates the resolution size, thus 1 file to get and run and answer questions.
Bloatware may be added to customize roms. The reason they are customized.. Right Even factory roms have it, don't like it.. well...
So little memory, so many apps.. 1g, 2g.. well Malaysk does the FUSE trick which opens up the full memory. Booroondook, I don't recall, maybe maybe not. ###8310 has it set to 3g right now I think, but I think there might be choice of default.
Malaysk has customized Launchers. JY5.1.1 typically (one other too)has a speed display on his 4.4.4 and 5.1.1 roms
Booroondook has a few and DSA8310 is mostly clean and factory based (Klyde)
###8310 uses what factory firmware uses. The Windows like and some other with the old time flip card time piece.
You may install the rom image via MicroSD card (plugs normally into the GPS slot) or the USB port 0 (Normally the Mini port front plug thingy behind the door)
If you have update.img with mcu.img, both will get programmed to the device.
If you are going from factory to any rom, you should do the wipe data/factory cache option after the rom is flashed. You can do this anytime after the reboot. And the 1st reboot takes a long time.
If you go from and DEVs rom to another, do the data/factory cache wipe option as well, in fact you can do this anytime you update.
Stopping here since at work and will edit and add later. This is the start.
##8310, Typos1 and others, I like input..
If you had a problem and fixed it, let me know
Hands Free Messaging
If you want to hear and reply to messages on your radio from your cell, get the app from Google Playstore readitotme and install on your phone
Under Profiles: Make sure you link it as "CAR KIT" and enable it
And set to BT Mono
If you want voice reply, enable that (you get 2 weeks free) and you'll need to download addition app
It will automatically use your Messages app on the phone for the app. So under the Apps, do not enable it.
But you can select additional apps and how you like to hear them Header, message etc
Under Contacts, you can also what to hear.. One area has ALL, so selecting anything under that will enable ALL contacts with that feature.
Other features and more stuff are listed, but this should work fine.
Adding Launchers from 5.1.1
5.1.1 update.img:
Both Malaysk and Booroondook load their images with a few launchers. If a launcher is in their ROM image, you can grab it from the image by using a program called "RK3xxx Firmware tools" (google it)
Simply load the update.img via the tool (select Img... box) , extract it (Extract under Firmware image tools), then extract again under System.img tools.
Then "Open folder..."
Locate folder "priv-app"
Find the launcher you like (Launcher2mtc3_5_1_1) example
copy to a USB flash drive
Some launchers use weather on their screen, so grab the weather one too folder "app" (MTCWeather) and copy to the USB Flash drive
take the flash drive and reverse the procedure.
To copy from the USB flash drive to the system, look for "mnt" in root of the device. Find the usb drives and locate your drive.
Copy the MTCWeather to "app" (this will make it appear in the apps folder) and set permission to 755 for folder and the apk in the folder 644 using Root Explorer
Copy the (Launcher2mtc3_5_1_1) launcher to "priv-app" folder and set permission to 755 for the folder and the apk in the folder to 644
Reboot
I have been trying to get the JY5.1.1 speedo to work.. ran out of time.. WIP
Test MCU and Factory ROM
MCU= KLD6-V2.91 (from Factory)
ROM= 5.1.1 (800x400 Pumpkin)
Radio had MAL 5.1.1 800x Aug file.
Fuse vs Standard RAM
1st: Flashed MCU from V2.97 to V2.91
2nd: Flash Factory ROM.
Reboot had issue,
3rd: Did a Data/Factory Cache and Wipe..
4th: Flash Factory ROM again.
5th: System rebooted to Factory Images
Results are that V2.91 and Factory 5.1.1 works fine. Will be adding apps and place JY5.1.1 launcher soon. (Can't, no root!)
The settings retained Factory settings
The About Device says MTCC -KLD6-V2.91 5.1.1 800x480
Its all good from MTCB
Oldpapa49 said:
Test MCU and Factory ROM
MCU= KLD6-V2.91 (from Factory)
ROM= 5.1.1 (800x400 Pumpkin)
Click to expand...
Click to collapse
Hi OP,
Three weeks ago i bought an MTCB KLD6-V2.86 w ROM 5.1.1 840x400 Pumpkin, ori release May 04 2016
Now got from pumpkin a rom from 05 August 2016 which works much better (reboots on button press in settings are gone...). The MCU stays on V2.86...
Q: whats the difference between KLD6 2.86 and KLD6 2.91 or KLD6 2.97 ? Are they just Upgrades or different functionality ? Is it dangerous to flash a 2.91 over 2.86 ? Will it bring features ? Are there mcu roms inside Malaysk Roms? For KLD6 the latest Version i could find on servers were 2.85. I would like to remap some keys to other functionality (eg Band or Scan to Mediaplayer...) maybe possible with Xposed ? Is Malaysk with preloaded Xposed the better choice ?
eblackie said:
Hi OP,
Three weeks ago i bought an MTCB KLD6-V2.86 w ROM 5.1.1 840x400 Pumpkin, ori release May 04 2016
Now got from pumpkin a rom from 05 August 2016 which works much better (reboots on button press in settings are gone...). The MCU stays on V2.86...
Q: whats the difference between KLD6 2.86 and KLD6 2.91 or KLD6 2.97 ? Are they just Upgrades or different functionality ? Is it dangerous to flash a 2.91 over 2.86 ? Will it bring features ? Are there mcu roms inside Malaysk Roms? For KLD6 the latest Version i could find on servers were 2.85. I would like to remap some keys to other functionality (eg Band or Scan to Mediaplayer...) maybe possible with Xposed ? Is Malaysk with preloaded Xposed the better choice ?
Click to expand...
Click to collapse
MCUs are improvements. It is odd that your unit is V2.86 , but it now says that KLD6-V2.86 will allow 5.1.1 work. Can you find typos1 and tell him you have a MTCB unit with 5.1.1. dated Aug 5th. 800x480 image.
I use to have KLD6-V2.81, Pumpkin told me they had a newer one and it is KLD6-V2.91. I have installed KLD6's 2.83, 2.85. 2.91, 2.95 (I think) and 2.97
Just remember to get your FACTORY Settings recorded. so you can set the right info.
MCU file are not attached to any ROMs by any Dev.
Dev roms are rooted and they supply a remap apk for keys. I have never used it.
As in the 1st post, DEVs develop the ROMs to their likings. Since you are on 5.1.1, DSA8310 has a pretty clean ROM and will chnage you MCU to look like a MTCC unit.
Since you have a MTCB, you might be able to go between 4.4.4 and 5.1.1. But make sure you have all the info settings in factory, Very important!
I'm just a basic person and like certain things... So I look and set my HU to my likings.
I change my ROM evrytime a DEV makes a change to tests. I'm on MALs latest 4.4.4 ..
Note: I rarely use radio, I use Sirius App. Radio signals stink where I live.
Oldpapa49 said:
MCUs are improvements. It is odd that your unit is V2.86 , but it now says that KLD6-V2.86 will allow 5.1.1 work. Can you find typos1 and tell him you have a MTCB unit with 5.1.1. dated Aug 5th. 800x480 image. *i did*
As in the 1st post, DEVs develop the ROMs to their likings. Since you are on 5.1.1, DSA8310 has a pretty clean ROM and will chnage you MCU to look like a MTCC unit.
Since you have a MTCB, you might be able to go between 4.4.4 and 5.1.1.
I'm just a basic person and like certain things... *so am i*
Click to expand...
Click to collapse
Thanks for this detailed answer! As i know now i can step back to 4.4.4 i will give it a try, maybe things are a bit faster then.... i also read in a Xposed thread, dsa8310 plans something about resoldering bigger RAM's, sounds interesting! Maybe i can find one who can do this for me and take away the laggyness, but first i want to do this Sound-Chip-Mod which looks easy to do, as this unit here has only poor sound and settings to offer... If the device survives, i will play around with the rk3xxx_firmware_tools
Oldpapa49 said:
MCUs are improvements...
Just remember to get your FACTORY Settings recorded. so you can set the right info.
... But make sure you have all the info settings in factory, Very important!
Click to expand...
Click to collapse
Just a few points to add:
1) In general we can assume that a higher rev MCU has better features/fewer bugs than a lower rev. (Otherwise why would the authors bother to create it?) But as @pa.ko has cautioned several times, that is not necessarily always true. There is some risk that a higher rev may seem to work fine, yet introduce subtle bugs that don't show up right away.
So while it is generally good to install the MCU image with highest rev #, it is also really important to remember which MCU you had originally, and make sure you have a copy of that image before you upgrade. Then if you do come across something that seems like an MCU bug, you can revert to your original MCU image to see if it goes away. If you can't get the exact rev#, then you will want to have the closest rev# to your original.
Note that there is currently no way to "upload" an MCU image from your HU, so you can only get them from the HU vendor (or from a fileserver).
2) You can save the "factory" settings to a 516 byte file called mcu.cfg; the option is in the factory settings area (behind the "126" password). You can then reload the mcu.cfg file and it should restore your factory settings to their prior values. There is no guarantee that an mcu.cfg file from a lower rev MCU will be compatible with a higher rev MCU, but they usually are (in my experience anyway).
Incidentally, 512 bytes of that 516 byte config file get downloaded into the MCU's memory (the 4 other bytes are a short header "MTC" and a checksum byte), and that memory area then configures the "personality" of the MCU. There is a one-to-one correspondence between the bytes of the config file and the bytes in that memory area in the MCU. If you look at the mcu.cfg file you will see that most of those bytes are zeros.
dhmsjs said:
Just a few points to add:
1) In general we can assume that a higher rev MCU has better features/fewer bugs than a lower rev. (Otherwise why would the authors bother to create it?) But as @pa.ko has cautioned several times, that is not necessarily always true. There is some risk that a higher rev may seem to work fine, yet introduce subtle bugs that don't show up right away.
So while it is generally good to install the MCU image with highest rev #, it is also really important to remember which MCU you had originally, and make sure you have a copy of that image before you upgrade. Then if you do come across something that seems like an MCU bug, you can revert to your original MCU image to see if it goes away. If you can't get the exact rev#, then you will want to have the closest rev# to your original.
Note that there is currently no way to "upload" an MCU image from your HU, so you can only get them from the HU vendor (or from a fileserver).
2) You can save the "factory" settings to a 516 byte file called mcu.cfg; the option is in the factory settings area (behind the "126" password). You can then reload the mcu.cfg file and it should restore your factory settings to their prior values. There is no guarantee that an mcu.cfg file from a lower rev MCU will be compatible with a higher rev MCU, but they usually are (in my experience anyway).
Incidentally, 512 bytes of that 516 byte config file get downloaded into the MCU's memory (the 4 other bytes are a short header "MTC" and a checksum byte), and that memory area then configures the "personality" of the MCU. There is a one-to-one correspondence between the bytes of the config file and the bytes in that memory area in the MCU. If you look at the mcu.cfg file you will see that most of those bytes are zeros.
Click to expand...
Click to collapse
Ina cases of issues with/after loading mcu.cfg (problems, incomparibility,...) you may reset my to default (factory default / clear) state by creating empty mcu.cfg (don't forget to check permissions)
Empty MCU.cfg forces MCU to reinitialise ... At least Russians are saying so, in some previous MCU vers, I didn't check in code for myself
Truck with empty MCU.cfg reset us better than reglazing my as reglazing is not overriding that particular memory area of config params
Call Home...
Ok, I have tried this on 4.4.4 and 5.1 (both roms)
1. Works better on 5.1 and not 4.4.4. It seems to crash google using 4.4.4 unless I did something incorrect.
2. You need to get the mtcservice (headunit 2.34 or 2.35) to make it function. I tried the one off playstore and I just don't really know about it.
When you use the mic to call the 1st time, make sure you select 'mtcsevice' (steering wheel icon) to make calls. It should complete after.
Related
First things first! As the topic states, this is a *TEST ROM*
DO NOT expect this ROM to be usable for every day use
DO NOT expect this ROM to be well tweaked for performance
DO NOT expect this ROM to ... you get the idea, i hope!
This is the first Test ROM for the Image Update service - this ROM has a 1024KB free space buffer for NK partition, 20MB free space for OS partition. This should be enough to facilitate several ImageUpdates for testing. (It's not intended to have enough space for you to add all your chosen apps for every day use - this is just for TESTING!)
It's based on WM 6.5 21812. This ROM is unique in that both the NK and OS partitions are completely uncompressed, rather than using either XPR or LZX - so i'm testing that too. Please report on overall system performance of the BUILT IN applications (not cabs or packages you install) - i'm wondering if Uncompressed is viable at all vs. XPR and LZX. So far i'm thinking no (60MB LZX -> 80MB XPR -> 150MB Uncompressed) - but testing is warranted!
The Image Update packages for this ROM are now in post 2!
Here's the download link!
Again, this is BAREBONES, the ONLY thing it has is drivers and comm manager, this is done on purpose, so that we can have as few variables as possible while testing deployment
http://rapidshare.com/files/244900505/ImageUpdate-ready-ROM-Raphael.rar
Some notes:
The ROM has an OS pagepool size of 26MB
The ROM has a ULDR pagepool size of 4MB (up from 1mb)
All compression is disabled entirely (not XPR or LZX, but Uncompressed - both on NK and OS partition, also compression is disabled on individual modules and files)
Dr. Watson (Error reporting) buffer reduced from 300K to 0K
Update Packages
QuickGPS
EzInput+eT9
Camera - This will install the Camera, Dshow, Mhub, and SensorSDK packages (Camera is dependant on the others)
Here's the test case scenario - create a directory named "Release" in your filesystem, at the root \ folder (so \Release)
Copy the cab.pks to your device, or sd card, and run it as you would a cab
Note any errors or anything that might occur before the process succeeds or fails
If the process fails - please attach the logs found in \ and \Release to a post, so we can analyze it further
If it succeeds, time to hard reset your device!
Check and see if the package remains after hard resetting.
If it does - We have a winner
A live-updating rom with no need to reflash the device after each upgrade? I love it!
Keep up the good work!
Interesting concept.
this is awesome! cant wait to cook one for kaiser(hint, hint) thanks for all your work, this is going to change EVERYTHING.
Image Update System
I have been following the WM Image Update System thread and the idea sounds very doable. How can we help?... David.
I can Hard reset my phone every day, so if you in need of any volunteers Im here .
I have been following your kitchens for a while, and it's time to return the favor.
Thanks so much for your hard work Da_G!!
-------
HTC Fuze - WM6.5 21812
Da_G...Sir, you are a saint and a scholar...when this is finished it will be the coolest thing since velcro...
I would love to help just let me know how...would be happy to test..report...etc.
Dreaming of the day...no more hard reset
Da_G,
Thanks for your hard work.
I'll been dreaming of the day when I don't have to reflash my ROM or hard reset just to update the software.
I'll beta test and give you report.
D/Ling now, will report after work this evening. :excited:
i am really enjoying the speed. its unreal. every thing else seems normal. i am still loading up my apps right now. i'll post up some more when i get home.
the speed and respon se is secon d to none . i am very much plea des with the performance .
i know you said its barebo nes....so. i will view the lack of came ra e xe and .net. fram ework as by design . let me know if there is anyt hing spe cific you want me to test .
rzanology said:
the speed and respon se is secon d to none . i am very much plea des with the performance .
i know you said its barebo nes....so. i will view the lack of came ra e xe and .net. fram ework as by design . let me know if there is anyt hing spe cific you want me to test .
Click to expand...
Click to collapse
I'm going to need you to test your awesome space bar, it seems to be more than working well... =P
LOL, didn't overwrite CompIME.dll in this release (again for compatibility reasons) so that's why the jacked up spacebar..
But hey, it's a test
Hoping to have packages for you soon
Everything is working smoothly, no issues yet. I read your other post on the image update and want to know how far into user customizablity we can go without messing up the update process, ie. regedits, packages, etc.. Or if its a secure core that we can't really mess up.
Oh, yeah, its supper snappy and extremely responsive. And running at 26% Memory isn't bad either.
Is it safe to assume any updates needed to be deployed, such as over writing the CompIME.dll will be done thru the this new Updating system, correct?
Thanks for your hard work Da_G!!!
So, am I correct that any chefs who want to incorporate the working updating system into their roms will have to cook unprotected? This could get really interesting, LoL.
Thanks for the awesome work!
@Farmer Ted:
Yes, to support Image Update, ROM's will need to be fully "unprotected" - protection is really just damage to the ROM structure that still allows the phone to work
@NFRCER:
Yep, that will be one of the first test packages probably
@danthman2000:
The only thing you need to be concerned about in doing mods is that any files you replace or registry settings you change that might be in a future update, the update will not apply them, unless its specifically set to override your settings by using an mxipupdate_*.provxml - but the creator of the package should be aware of this before hand - so if it needs to override any of your settings it should be set to.
By the way, I plan to have the first test .cab.pkg up by tomorrow, so if you're sitting there with the test rom flashed, might wanna go back to a working one for now
Da_G said:
@Farmer Ted:
Yes, to support Image Update, ROM's will need to be fully "unprotected" - protection is really just damage to the ROM structure that still allows the phone to work
@NFRCER:
Yep, that will be one of the first test packages probably
@danthman2000:
The only thing you need to be concerned about in doing mods is that any files you replace or registry settings you change that might be in a future update, the update will not apply them, unless its specifically set to override your settings by using an mxipupdate_*.provxml - but the creator of the package should be aware of this before hand - so if it needs to override any of your settings it should be set to.
By the way, I plan to have the first test .cab.pkg up by tomorrow, so if you're sitting there with the test rom flashed, might wanna go back to a working one for now
Click to expand...
Click to collapse
A working one? This one is working beatifully lol .
Im curious, I checked the system tab, and I didnt see the Windows Update Icon...
How will we check for the update then? Just wondering, thats all.
My apologies if im asking too many questions
Great news Da_G. I'll test it once you post the update tomorrow. How do the updates get delivered?
Is the .cab.pkg a small file which contains the server information so the phone can go out and retreive it? Or is the .cab.pkg the whole kitten caboodle?
Update: New release (RLS 5)
-Comes with 'rogue tools' for overclocking and setting display density will need an update over market to support nike, myn told me he will push it to the market during the next day or so)
-feels smoother, connectivity seems to be a lot better (I never had a faster browsing experiance on my nike than with this build and opera mini), rejoining network after lost signal also seems to be faster
-nice new weather/clock widget
-if you use installd version, the androidupdate.tar from rls4 is still necessary for powermanagement
Myn's new (16.03.2010) Donut android build runs quite smooth on nike! Finally a decent alternative to Ion on nike.
Get it from the vogue forums (SQSH version):
http://forum.xda-developers.com/showthread.php?t=619980
Here is a link to the basefiles I am using:
http://84.23.71.227/kerneloftheday/RootfsBasefiles20100318.zip
The kernels are from dzo's branch with a few minor fixes (vibration, irq-wakeup, red led blinking when in sleep mode). Additionally the kernels should work with enabled HW3D in eclair with boot parameter hw3d.version=1 (not tested yet...).
HowToInstallInANutshell:
-delete old android files from sd
-extract basefiles to sdcard
-extract system.sqsh from myns package and copy to sd
-if you are on a nike100 make sure deafault.txt points at the kernel without vibration (included)
-otherwise default.txt should be fine, most parameters are ignored anyway.
-run haret
-be happy
Impressions:
-sleepmode 1 ok, wakes up, red led blinking. Battery life seems ok, but i only tested a few hours...
-very fast
-many locales, not just english like in good ol' ion
-quite stable net, nice apn autodetect (just had to select from two alternatives), working google stuff
-still not working: bt, incall volume, cam
So, give it a shot and leave your impreesions here!
mblaster
********** UPDATE ************
Installation with the NoRootfs Method is now possible with working net and powermanagement. This gives us the possibility to use the Themes and the default font and everything else that can be provided via androidupdate.tar
See the Wiki for installation instructions. Make sure that you have the provided 'androidupdate.tar' (see attachment, file is in the zip archieve) in your andboot folder along with the androidinstall.tar when installing.
To install themes just copy them in you andboot folder (must be named androidupdate.tar), reboot into menu -> update (-> fix permissions).
PS: Doesn't seem to work with eclair builds, but could work with other donuts
PPS: This should also work with ext2, if someone tried successfully please let me know. €: Works with ext2
Additionally the kernels should work with enabled HW3D in eclair with boot parameter hw3d.version=1 (not tested yet...).
Click to expand...
Click to collapse
you've added hw3d support? I tried to do that - all that I got is 3D without textures or simply nothing - black screen. I did same as in this commit in repo.
I did the same. The only build i saw it working was aosp eclair for kaiser (gallery3d worked). Otherwise i got the same errors. I read that the other devices suffer from similar problems.
Ps: Writing this on myns donut. Everything stable so far.
mblaster said:
Myn's new (16.03.2010) Donut android build runs quite smooth on nike! Finally a decent alternative to Ion on nike.
...
So, give it a shot and leave your impreesions here!
mblaster
Click to expand...
Click to collapse
Hi mblaster,
works like a charm here. Very fast and stable. This is the first ever Donut Build with stable working Data i've seen....
Only Point is, that icons are really very small. Seem to me even smaller than in the old Cupcake Releases with 320x480...
Tried higher settings for lcd.density, but screens don't fit than anymore.
Have you tried it with a non modded system Image ?
Greetz, lagloose
ECLAIR
because you are starting another section of the eclair?
already has almost no one accessing the other thread ...... I have a question there for two days and no one responds more ..
I am very impressed with the progress of the android in my eclair NIKI100 (20 keys)
is making calls, receiving messages, all volumes of the system are working (calls, music (I had to install another player why that came standard did not work), alarm etc. ..) I'm using it for three days, battery lasts long , it does not heat the unit, since I use it in everyday life.
now I have some questions for you:
is so difficult to operate the headphones?
I love listening to music, especially in the way of work, if possible, please someone do work ....
particularly hate wm, I think one day we niki users, we can get the WM and definitely use the android, (because you can try to do everything, are the gods of HTC ....).
another question, I can change the theme of the eclair? wanted it like this: http://forum.xda-developers.com/showthread.php?t=600154, it is possible??
I'm not charging, just begging! rsrsrsrs
Congratulations XDA....( GODS OF HTC)
Hi there,
together with mblaster's combination of basefiles in the first post of this Thread, the sqsh Version of the image in this thread http://forum.xda-developers.com/showthread.php?t=591104 works also...
mblaster; seem's you've found/made the ultimate combination for Donut Images. PERFECT !
Greetz, lagloose
Theming with Metamorph
I been reading around on Vogue's thread and Metamorph catched my attention. It can style up android theme. Is this apps runs well on this build. I am confused because based on this site http://www.androlib.com/android.application.stericson-xda-metamorph-xnFD.aspx it can only run n Rooted phones. What is rooted phones anyway and can this run well in nike100 with the android build posted in this thread?
When is the nand version available? I think the only thing missing now in nike100 are camera and vibration features. Great job!
More Power!!!
Anyone encountered the "Half Size" icon problem ?
This is, when there's a reload of the Home Screen, all icons are suddenly half the size than normal. I had this after leaving the Browser.
Couldn't find a solution for that behaviour. Any ideas ?
Greetz, lagloose
ohh, nice ROM, everything is fine except one - it says that my pin code is incorrect ;//
and what else.. is it possible to get to wifi on Nike using wifi-enabled android?
jefins said:
ohh, nice ROM, everything is fine except one - it says that my pin code is incorrect ;//
and what else.. is it possible to get to wifi on Nike using wifi-enabled android?
Click to expand...
Click to collapse
You have to disable PIN in WinMobile afaik for all builds so far.
About wifi: The stickies say no wifi on nike. Never.
"never ever say never" ;DD
thanks anyway for Pin code tip.
Network problem
got two bugs here.
1. browsed from wm then switchd to android. i cannot connect anymore when in android. even if i reconfigure my apn.
2. switching from phon mode to airplane mode and airplane mode to phone mode will stuck in airplane mode.
@mblaster
how to enable apn autodetect?
@mblaster
First of all, good idea with the new wiki. Hope to add some things in the near future...
had the idea of creating system.sqsh files of all variants (Themes) of the original Vogue Thread. So i downloaded one of the androidupdate.tar files, und untared it "over" the files of the original ones in the androidinstall.tar file. Made an ext2 System and then a Squashfs System with genext2fs.
But no success....
Booting stucks obviously just before the Android Setup Wizzard should appear. Any Ideas ? Perhaps a permission problem ?
Greetz, lagloose
lagloose said:
@mblaster
First of all, good idea with the new wiki. Hope to add some things in the near future...
had the idea of creating system.sqsh files of all variants (Themes) of the original Vogue Thread. So i downloaded one of the androidupdate.tar files, und untared it "over" the files of the original ones in the androidinstall.tar file. Made an ext2 System and then a Squashfs System with genext2fs.
But no success....
Booting stucks obviously just before the Android Setup Wizzard should appear. Any Ideas ? Perhaps a permission problem ?
Greetz, lagloose
Click to expand...
Click to collapse
me again...
just got a flash in my brain...
probably a story about the rootfs because of different load types (NoRootFs vs. Classical sqsh File) ?
so what about mounting the original sqsh Image and untaring the update "over" the rootfs ? ...
@lagloose: Might be an issue because the androidupdate.tar files are made for norootfs. Perhaps its time to move on to an installed version without rootfs...
@ebautista: Sorry, but I do not maintain myn's build. Perhaps it would be a good idea to report bugs in myn's thread in the vogue forums. APN detection worked for me right out of the box. Do you use the basefils from this thread?
€: your brainflash was faster than my typing... but perhaps you should at laest try to set the right permissions, it might work
Hi all,
Just tested sqsh Image from http://forum.xda-developers.com/showthread.php?t=628459. Not completely tested but seem to work also with our basefiles.
I'm working on a way to get themed Images for us Nike Users. Still some problems to solve, but shouldn't be that difficult...
As soon as i've found a way, i'll state it here.
Greetz, lagloose
I really would suggest to move on to NoRootFs for various reasons:
The theme packages are already available there
The basefiles are still supported and regularly updated, while SQSH is dying out, and as there are very few devs for nike we should try to profit from the progress made on other devices
There should be no drawbacks, just a few more MB on sd-card for the system
The installer for systems / updates is extremely useful (theming, installing your favourite apps in one shot ...)
Give it a try, you will find a little howto and links to ressources in the wiki
mblaster,
€: OK, I have good and bad news. The good news is that it seems like you can keep your datafile after switching to norootfs. The bad news is that sleep doesn't work anymore (same settings/build/kernel) -> The problem that prevents us from using more recent builds seems to exist inthe basefiles!!!
Basically thids leaves two possibilities: Either its in the part of the nonexistant rootfs that now is part of the system, or (my guess) it is in the initrd. At least it does not seem to be a problem with the kernel.
mblaster said:
...
€: OK, I have good and bad news. The good news is that it seems like you can keep your datafile after switching to norootfs. The bad news is that sleep doesn't work anymore (same settings/build/kernel) -> The problem that prevents us from using more recent builds seems to exist inthe basefiles!!!
Basically thids leaves two possibilities: Either its in the part of the nonexistant rootfs that now is part of the system, or (my guess) it is in the initrd. At least it does not seem to be a problem with the kernel.
Click to expand...
Click to collapse
..same here after trying. I also couldn't get a Data Connection. Obviously Network Device ppp0 is missing. So i'd guess, that your guess concerning the initrd is correct. Unfortunately, i won't have the time to look after the problem in the next days. So for now we still have to use the SQSH files, until the problems are fixed...
hi, mblaster,
i want to download the file as "Get it from the vogue forums (SQSH version):
but i cant aceessed "mediafire"
Could you email to me a file that it can running on nike100, thnks
my mail is [email protected]
See Post 1 for UPDATE!
lagloose said:
..same here after trying. I also couldn't get a Data Connection. Obviously Network Device ppp0 is missing. So i'd guess, that your guess concerning the initrd is correct. Unfortunately, i won't have the time to look after the problem in the next days. So for now we still have to use the SQSH files, until the problems are fixed...
Click to expand...
Click to collapse
I am quite sure now that the initrd is fine and the problem is in the Rootfs, or better what is left of it. The latest working basefiles include a Rootfs dated to 2009-11-16. There is a newer Rootfs on sourceforge (sometime in december 09) that shows the same problems (net/powermanagement/shutdown). As parts of the rootfs are included in the androidinstall.tar images, thos errors are still there. My update file (now included in post 1) overwrites those files with versions from the 11/16 rootfs. That leeds to a working system (with the new initrd).
Unfortunately the update is incompatible with the newer eclair builds that are around. Seems like they use another rootfs that rejects the old files...
Does anyone maintain a git repo of the rootfs? It would be interesting to patch the problem for good
Hi.. I have been trying to fix a tv stick for a few months now (basically is more about the knowledge i am getting - I am not desperate in fixing it). It is a strange piece, probably clone that i have been tricked in buying. It has an Allwinner A20 dual core cpu with an AP6210 wifi module...
Tried to flash another firmware ti improve it, ended up with the wifi problem. Wifi (and bleutooth) will not start. When i press the button, it just slides back to off... I have read and tried anything i could find on the internet. I have also tried tens of firmwares, but the wifi problem persisted (the original firmware is nowhere to be found).. To cut the story short, the device will not connect to a computer through ADB (it just doesn't seem to support this function - is not a matter of drivers). So everything i have been trying did not include this option...Also the recovery can not be changed to support backup and restore from custom recoveries (i.e CWM, or TWRP)..
What i did manage was to extract a backup from the rom, of another identical device, with the Nandroid App (online version, not through the recovery). Then i used the Dragonface program to edit another similar firmware (MK808C). While loaded, i open the FSOP folder which is the folder that dragonface collapses the loaded firmware for editing and then, i replaced the existing system folder with the one i had backed up trough the Nandroid procedure... Then hit the save button of the Dragonface...
I flashed the new *.img to my tv stick with the phoenix tool, and the tv stick booted normally, looking EXACTLY the same as when i first bought it. I even managed to get the bleutooth going this time, BUT, the bloody wifi still refuses to come on :-/
I must tell you, I know my way through some computer technical stuff but I am not an expert into the coding level and i haven't had the experience of Linux systems (thus i don't really understand coding). I really thought all settings and drivers are included in the system file and copying the original system file into another firmware, would do the trick.. but i guess is not that simple... The thing is that, the way i see it, the problem is probably hidden at the booting level... hitting the system configuration in the advance settings of the Dragon face, will open some coding thing which i don't understand.. but i do see the AP6210 module in that coding, which means that the new firmware includes those drivers..If anybody have any idea or can point me to the right direction I would really appreciate it.. Thanks
I have the same problem with AP6210 on H3 Allwinner STB box. After firmware ugrade from Android 4.4.2 to Android 10 Wifi just don't work, button slides back to off. Drivers are present. Have both firware files unpacked.
Please help! What i have to do? Sys_config? Init.rc?
Hello guys,
I have a problem when using Poweramp music application.
I always used the application sorting songs by modification date (that way, it plays the latest music first).
I used CM 12.1 when used this way. (It worked correctly sorting by date modified files).
But after Flashed the jelly bean stock ROM, (I blinked with 6 GB PIT), sorting by date of modification does not work anymore ... (both ROM jelly bean stock, as in CM 12.1 (which I am using again ).
When you sort by file management applications, correctly classify the songs.
Can someone help me? (I have already sent a bug report to pweramp team, but they said that some devices fail to read the timestamp, but I always used that function, only now does not work.)
Note: already activated the option into Settings> Folders and Library> Lists and tick "Sort By Filesystem Date / Time" (does not work)
*What do I do? No problem if you delete all my data in a procedure, the only requirement is that I want to use the CM12.1.
Thank you so much.
Good morning people,
I managed to solve the problem.
Despite the explorers get properly classifcar the files by date modified, do not know why the poweramp could not do it (tested my memory card in two other mobile phones with poweramp, and presented the problem).
The solution was: Move all the songs to your computer, and then copy back to the memory card, so that old songs were glued first (In Windows, enable the date modified column, press upon it, the old songs should appear at the top, done that, select all, copy and paste the card. the new songs will be pasted last but with that the date / time change is more recent). When I did this, the songs have replaced the modified date for the current date, and have been classified correctly.
Simple and strange, but it worked. : D
Thanks
Hi,
I've been trying to locate the "boot photo" on an Amlogic S912 TV box that I have in order to change it. It is the first image that you see when you power the unit on, followed by the boot video which I have already changed and is located in the "etc" folder of the unit. I cannot find the location of the initial photo though. If anyone can tell me what folder it is located in I would certainly appreciate it! I believe it is either in bmp format or png format. The unit is running android 6 and these are the folders that are in the unit. (If this question is in the wrong section I apologize in advance!)
Thanks for any help anyone can offer.
It's not gonna be there. That image is stored in one of 2 places in every device I have had. It was either on the boot partition or bundled with the kernel. Either way you would have to flash the device to change it.
I just discovered that it is in the "logo.partition" which shows up in temp/ level 1 with the Amlogic Customization Tool, but I'd like to find out how to modify that with my own photo and then repack the firmware. Any ideas?
fxbill said:
I just discovered that it is in the "logo.partition" which shows up in temp/ level 1 with the Amlogic Customization Tool, but I'd like to find out how to modify that with my own photo and then repack the firmware. Any ideas?
Click to expand...
Click to collapse
You would need to extract that partition and find the file that it is placing in temp. Change the file and refresh the partition. Mind you this is dangerous and doesn't always work. But as long as you ha e an unlocked bootloader you should be able to recover.
The "logo.partition" is a single file in the level 1 temp file directory. It is actually a single file type, but I don't know how to disassemble the file or what program would open it. I can get a hex editor to open it, but that doesn't help me much since it is a 6 megabyte file and the hex, of course, is unreadable...at least to me. There are about 20 files in the level one temp folder of which this is just one. The program works just fine with Amlogic devices that are running Android 5 and below and does almost everything with Android 6, but this is one of the things that it won't do in Android 6 and the Customization program has not been updated for a couple of years. I'm hope that eventually it will be but at this point I need another way or program that will allow me to do it!
Found it..... It's in the Level 2 folder. Easy to put into the firmware once you know where it is!