Related
Is it technical possible ?
You know like on old mobile phones - alarm clock wakes up device and you hear Alarm even if your phone was turned off.
I think such modern processors definitely must support wake-up functions and it's independent from WM OS.
Would like to hear answers from knowing people.
Thanks.
I'm also interested at this Question!
Also interested in this solution
Nice question, that keeps on popping up for new WM-users...
For the moment it is impossible, due to many hardware design-changes that would be necessary and these would produce a severe amount of OS-standard-changes. (clock/poweron has to be abstracted as device, kept in synch with old-fashioned internal clock for compatibility, etc)
If M$ decides for this fundamental hardware-addon/change for WM7, (as I would do if I were they), I will throw in some discussing charged elements:
The HTC HD2 will not fully comply to WM7 standards, due to missing standards
OR
HTC has already accessed M$ holy white papers for WM7 and already made it pre-compliant. (I would doubt this)
In the end, it will be a guess, if no HTC engineer clicks in here.... but for now at WM6.5 stage - a simple NO is all I can tell.
MS have already published the WM7 compliance specs, and none of this is in there, people have been asking for it (not sure why?) since WinCE4 days (WM2003/WM2003SE) and MS have done nothing to add it.
Like I say, not sure why you would want the device off? if you dont want it to ring etc, just put it in flight mode, hardly uses any battery in that mode anyhow.
Like I say though, it's not coming anytime soon, if ever, and a lot of other 'smartphone' OS's dont have it either.
Hello,
Thanks for your answers.
Really... I thought this "wake-up" functions is platform independent. Anyaway I'm pretty sure Processor chips support this function. MS doesn't make they own chips. So I suspect it's how that Windows Mobile BIOS is built.
Or I'm wrong?
The Windows Mobile platform does not use a BIOS as such, that functionality is taken over by the SPL layer of the device (and the Radio Stack in some parts)
So, nope. Like I said though, why do you want it? Android and iPhone don't do it either, so it's not like its a WinMo only thing (some of the latest Nokia's dont do it either)
the_ape said:
The Windows Mobile platform does not use a BIOS as such, that functionality is taken over by the SPL layer of the device (and the Radio Stack in some parts)
So, nope. Like I said though, why do you want it? Android and iPhone don't do it either, so it's not like its a WinMo only thing (some of the latest Nokia's dont do it either)
Click to expand...
Click to collapse
Maybe you're right, cause with turned off display my phone power consumption is very low.
But I consider it's a useful function.
I had an accident when someone stole my old Nokia 7210. That person turned off phone, but I was able to find it because I've heard alarm sound, which played. =)
arcades said:
Maybe you're right, cause with turned off display my phone power consumption is very low.
But I consider it's a useful function.
I had an accident when someone stole my old Nokia 7210. That person turned off phone, but I was able to find it because I've heard alarm sound, which played. =)
Click to expand...
Click to collapse
Spose, however just use Exchange or MyPhone and you can get the location of the device back over the web much easier
Turn：mikeyangly（Come from：pdafans.com）
Touch screen, and drive signals are not supported, I hope the faithful machine can solve this problem
System Download:rayfile.com/zh-cn/files/4e80a502-973c-11df-abb4-0015c55db73d/
GREat news !! hope its just a question of time for the others drivers!
On my neotouch android doesn't boot. It stays on this:
EDIT (22:05): now it boot. I haven't got in the root of Storage Card .
s200 froyo 2.2
O ye,this is a very great news,incredible ,we jump directly to Froyo 2.2,as you say it is a matter of time and developers now.The waiting has began!
Otherwise phone boots very quck:
-no touch
-no sound
-no keys
-no gsm ...
we hope all will be on soon
good start. hope problems are possible to be solved....
Oh very goog!!
Does tsamolotoff's TS driver works?
its drivers work with ubuntu!
Wow great news!I am waiting for a full working version(rom)
Android just has more free apps than windows..
that would be the only reason i would want android
free apps... oh well
The only reason i would want android is a bunch of games ported for this system. Android for games and WinMob for everything else. and all this stuff in one device. that would be nice
very good.
Why do I have blue screen after 10 seconds working of it?
Because there are many problems to resolve to use android on our s200...The os is not alredy usable like in htc hd2,and our device is not supported like the htc one.So maybe the project for s200 is end.I wish i could use android in my phone,but maybe i will never see a usable interface
This is an exciting good news. Soon we can use the Android system has. Thank you for your efforts.
Sadly theres no kernel/android dev that has an s200, so android partly working on it might never happen, unless a dev picks it up and starts making patches/fixes for the kernel.
Not so good if you think that s200 and hd2 project started togheter,but hd2 after 1 month has a usable android or ubuntu release and our s200 has only a not usable android "desktop".Our device is not supported by comunity as hd2,so correct me if i m wrong,but i think no one still working on android s200 release
Ok guys it has been a month since first post, anyone reckon this is going somewhere? who was developing this in the first place? I am willing and ready to help in any way I can (I have stated this before) if necessary. I have a working s200, but no experience in linux programming, although I could learn some basics if needed.
Maybe we could send some android devs a pm? I mean how hard can it be if our hardware is so similar to the Liquid, AND we already have it running on our processor...?
I have seriously considered leaving the s200 and getting an HD2 by now...
Greets
no news of any progress for a while now...
anyway i never expected a fully working android on our neotouch. theres just not enough guys working on it like on the HD2...
can someone mirror this file please?
i dont want to download & install rayfile's client...
Thanks.
It s a really hard porting job...Hd2 owner has a good partialy stable android port,but as you all know there's 20 times hd2 then s200.The problem on our phone is the restricted comunity support
Well, it seems that when I got my s200 broken nobody raised the banner from my cold hands
Now my device is up and running again, and maybe i'll try to do something more... don't expect ts to work in android, as it's completely functional via tslib, and i don't know droid's architecture to determine why this PoS of an OS can't use it... if you really want it guys, why don't you experiment with sequence of input_abs_* functions within ts worker thread in driver ? There're so many *experts* who make ROMs via kitchens or do fancy icons/pictures - take up your time and learn C / linux kernel... I started with barely basic knowledge of the first (and I was lucky with the fact that there're many pre-coded drivers that simply needed some testing, or with semi- or fully-compatible initialization (many thanks to dcordes, Cotulla and the team))
are there any risks to flashing my hd2 too often? and how long does they phone usually last before it breaks down from normal use?
Sent from my HTC HD2 using XDA App
bbot3k said:
are there any risks to flashing my hd2 too often? and how long does they phone usually last before it breaks down from normal use?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
I've flashed different WM6.5, Android, and WP7 roms probably over 100 times (not including all the radio flashes) and mine is running great with no issues. Everything works fine and I've had the phone for about a year. It's different for each individual unit but I wouldn't worry.
I've flashed mine at least hundred times with different OS-s (WM, WP7, Android SD, NAND...) and it's still 100% OK!
It's not how many times you flash it, It's how well you do the flash and how good the files are.
So if you read before you flash and you flash trusted files your device shall live for decades .
But if you always ignore the "Warnings" and flash untrusted files carelessly, your device may not see the day light of tomorrow .
-By trusted files I mean files compatible with your device and from a known developer
-By reading I mean reading thoroughly the entire post, and check the replies as well as they always contain first known issues .
- I remember a guy who has just bought his HD2, he wanted to install a custom ROM, he was told to upgrade his radio, after he did his device wouldn't boot. It turned out he flashed the incompatible radio for a Tmous .
The first thing I ever flashed was a custom 6.5 ROM on my Diamond about 2 years ago. I probably read like 20 threads and rechecked my files 10 times before I flashed the unlocker and the ROM. I've flashed custom firmware on many WM, android, and iphones since then and always read exactly what I need to do before I do it. You do see threads where someone flashed a CDMA hspl on a GSM device and vice versa or .51 radio on a tmousa HD2, or a froyo radio when not supposed to on an Evo or Incredible or something and brick their phones.
I think you'll be fine, just make sure you do the research and it's actually pretty easy not to do the stupid thing if you're paying attention.
orangekid said:
I've flashed different WM6.5, Android, and WP7 roms probably over 100 times (not including all the radio flashes) and mine is running great with no issues. Everything works fine and I've had the phone for about a year. It's different for each individual unit but I wouldn't worry.
Click to expand...
Click to collapse
I don't think that NAND Android and WP7 count, since they're flashed through MagLoader ?
kawazaki said:
I don't think that NAND Android and WP7 count, since they're flashed through MagLoader ?
Click to expand...
Click to collapse
true, you can only really brick by flashing a bad radio or bootloader.
Sorry for bringing this back up, I was about to make a new topic, but I figure lets keep it together.
Anyway arent there only so many writes that can be made to these chips? I mean, they were basically designed without this in mind. They knew for updates, but thats like twice a year, maybe 3 or 4 max. Not 100 times a month.
Please excuse me if I am wrong. But arent they basically like a SSD? Ive read they will last only so long because of the number of writes they limit then the cells die. Maybe we dont have cells, but still write times?
IDK, Im just not flashing as much as I used to, trying to keep it to a minimum. Havnt heard of anyone saying it wont flash anymore yet, so thats a good sign. Maybe the writes are in the millions?
Just some thoughts I had...
PS. I also noticed in one of my recovery.log files, it found bad blocks or sectors or something. Thats a bad sign of something...
theslam08 said:
Sorry for bringing this back up, I was about to make a new topic, but I figure lets keep it together.
Anyway arent there only so many writes that can be made to these chips? I mean, they were basically designed without this in mind. They knew for updates, but thats like twice a year, maybe 3 or 4 max. Not 100 times a month.
Please excuse me if I am wrong. But arent they basically like a SSD? Ive read they will last only so long because of the number of writes they limit then the cells die. Maybe we dont have cells, but still write times?
IDK, Im just not flashing as much as I used to, trying to keep it to a minimum. Havnt heard of anyone saying it wont flash anymore yet, so thats a good sign. Maybe the writes are in the millions?
Just some thoughts I had...
PS. I also noticed in one of my recovery.log files, it found bad blocks or sectors or something. Thats a bad sign of something...
Click to expand...
Click to collapse
That discussion is ongoing since the flashing thing ever exists... at least, updating your ROM with software from HTC or your network operator is technically the same thing...
I have read several times that those memory chips can stand like 1000 flashing processes, but I have never ever flashed any device that many times. With my HD2, I am probably, like many others in this thread, at 100 different ROMs, including WP7 and Android, in the meantime.
when you actually flash your device, you simply write some nand memory blocks with some data. The same thing happens when you..let's say..install any app to the phone's memory. theslam08 is talking about the comparison between nand memory and ssd hard drives. Yes, they are the same thing in almost every aspect.
Because i happen to have studied nand flash chip datasheets from different manufacturers i can tell you some things. The internal memory of a phone is managed dynamically. Therefore, when you flash a rom, it will not be written on the exact same memory blocks as the one before. Different apps you install will also have different positions. Also, the flash controller chip (i believe it to be an atmega 32-64 microcontroller - for hd2) also makes sure that no individual block gets overwritten more often than other.
The only things that always have the same memory addresses on the chip itself are the steppingstone, ipl-spl chain and rom headers. If they are not in the exact same position the snapdragon chip cannot read them, it's hardwired to search for them in that exact spot. So if there were a real risk to flashing, these software parts would be most vulnerable. How much? Well, if i am to quote samsung and it's KS series nand chips (about 2007 generation, now things are better) each memory block should withstand about 100.000 write operations under normal conditions. Please take note that read operations doesn't count since they don't actually change the state of the memory block. This would signal that you can technically flash the ipl/spl (or hard spl) about 100.000 times.
About the rom itself, since it's not written on the exact physical block each time (the nand memory controller prevents this) it should be possible to reflash it, in theory, some million times. Actually the flash itself is a pretty basic file copy operation, the rom content is copied to the nand memory and then it is run from there. If you think flashing can damage the phone in time.. well think of the temporary processes involved when simply ..running the phone. Various temp files are written, other files are modified, apps are installed and create their own registry settings (if we talk about win mobile) those keys generate another write cycles, the temp files yet another write cycle and so on. By comparison, the actual flash operation generates fewer write cycles then.. let's say, about 10 phone soft resets or couple of days of normal - light usage.
Don't worry about that. About nand memory performance and write cycles.. another example.. i have a 8gb cf card onto a netbook motherboard. The cf (compact flash) card, is mounted as a hard drive and the OS - windows xp, boots form it and it's been run along with some applications. That's A LOT of write cycles. However even the cheapest 8gb card - the one being used, managed to withstand one year of usage in this pattern although consumer grade cf cards are NOT made to run OS's from them. Even now the card shows no damage/corrupt blocks/dead blocks.
I've been using windows mobile pda's/smartphones for some 12 years, servicing them for about 8 years and in the later times i've begun flashing by jtag or other low level ways. I haven't yet seen a device with dead memory blocks .. that have simply died out due to wear&tear. Yes, memory can become corrupted, you can develop bad sectors, but not because of normal usage. Usually you get them if you fail a flash process (disconnect the phone during flashing of sensitive portions of the rom) or as a byproduct of CPU/MCU failure or errors.
facdemol said:
when you actually flash your device, you simply write some nand memory blocks with some data. The same thing happens when you..let's say..install any app to the phone's memory. theslam08 is talking about the comparison between nand memory and ssd hard drives. Yes, they are the same thing in almost every aspect.
Because i happen to have studied nand flash chip datasheets from different manufacturers i can tell you some things. The internal memory of a phone is managed dynamically. Therefore, when you flash a rom, it will not be written on the exact same memory blocks as the one before. Different apps you install will also have different positions. Also, the flash controller chip (i believe it to be an atmega 32-64 microcontroller - for hd2) also makes sure that no individual block gets overwritten more often than other.
The only things that always have the same memory addresses on the chip itself are the steppingstone, ipl-spl chain and rom headers. If they are not in the exact same position the snapdragon chip cannot read them, it's hardwired to search for them in that exact spot. So if there were a real risk to flashing, these software parts would be most vulnerable. How much? Well, if i am to quote samsung and it's KS series nand chips (about 2007 generation, now things are better) each memory block should withstand about 100.000 write operations under normal conditions. Please take note that read operations doesn't count since they don't actually change the state of the memory block. This would signal that you can technically flash the ipl/spl (or hard spl) about 100.000 times.
About the rom itself, since it's not written on the exact physical block each time (the nand memory controller prevents this) it should be possible to reflash it, in theory, some million times. Actually the flash itself is a pretty basic file copy operation, the rom content is copied to the nand memory and then it is run from there. If you think flashing can damage the phone in time.. well think of the temporary processes involved when simply ..running the phone. Various temp files are written, other files are modified, apps are installed and create their own registry settings (if we talk about win mobile) those keys generate another write cycles, the temp files yet another write cycle and so on. By comparison, the actual flash operation generates fewer write cycles then.. let's say, about 10 phone soft resets or couple of days of normal - light usage.
Don't worry about that. About nand memory performance and write cycles.. another example.. i have a 8gb cf card onto a netbook motherboard. The cf (compact flash) card, is mounted as a hard drive and the OS - windows xp, boots form it and it's been run along with some applications. That's A LOT of write cycles. However even the cheapest 8gb card - the one being used, managed to withstand one year of usage in this pattern although consumer grade cf cards are NOT made to run OS's from them. Even now the card shows no damage/corrupt blocks/dead blocks.
I've been using windows mobile pda's/smartphones for some 12 years, servicing them for about 8 years and in the later times i've begun flashing by jtag or other low level ways. I haven't yet seen a device with dead memory blocks .. that have simply died out due to wear&tear. Yes, memory can become corrupted, you can develop bad sectors, but not because of normal usage. Usually you get them if you fail a flash process (disconnect the phone during flashing of sensitive portions of the rom) or as a byproduct of CPU/MCU failure or errors.
Click to expand...
Click to collapse
Thanks for enlighten us
I have some bad blocks in my HD2, I always think that it is due to my excessive flashing habit. I flash almost roms avaiilable since I join xda
Now, it taken its toll. SOme nand android roms fails to flash and boot due to this bad blocks.
However, I still can flash wm 6.5 and runing SD Android without any problems
Cheers
silverwind said:
Thanks for enlighten us
I have some bad blocks in my HD2, I always think that it is due to my excessive flashing habit. I flash almost roms avaiilable since I join xda
Now, it taken its toll. SOme nand android roms fails to flash and boot due to this bad blocks.
However, I still can flash wm 6.5 and runing SD Android without any problems
Cheers
Click to expand...
Click to collapse
Well afaik, those bad blocks should be re-mapped so that they are not used when flashing roms.
Well thank you for that facdemol!
Its basically like I understood, just didnt really think the actual operation were the same for this chip and ssd. But thats cool, so it should be okay for a long time then .
As for the bad blocks, is there a way to 'chkdsk' on the nand? Do a clean up of the bad blocks or once bad they are always bad? Id like to clean those up. And no, I have never crashed a flash half way, ive only recently had some boot loops, thinking the bad blocks arent helping...
normally, the nand memory controller deploys error correction algorithms. On top of that, a technology similar to SMART (for hard disks) is used to both level out the wear of each particular memory cell and also to remove broken ones (either the ones that fail over time due to various reasons or due to manufacture errors). The MCU (microcontroller) also has a small internal memory used to keep a track on the situation of the memory blocks inside the nand chip. If for whatever reasons, some of them fail, the MCU will log this inside it's memory and also mark those sectors as "bad" thus preventing any write to them. At this stage the user won't see any problems with the NAND, yet. Once the MCU memory is full, further nand memory sectors that die out, won't be recorded and managed, therefore will appear as visible. In contrast with hard disks, were you can actually isolate those sectors and prevent them from being written, phone's don't do this, or more precisely their OS's don't support this feature. So, when you flash a phone with bad memory blocks, data will be written there but it won't be read at the next restart. So comes occasional restarts or freezes. If you're "lucky" you can get a bad memory block in the area where the ipl/spl resides. This is an end game scenario, since the ipl can't be "moved" around the nand memory.
You cannot effectively map the broken sectors of a nand memory once the mcu unit's memory is full. Those are here to stay. The only way i know involves jtag and some really fancy software tools that load a small program intro the phone's ram memory. That program runs from there and allows for a full nand memory checkup.
you probably have more chance of the god damn crappy micro usb or touchscreen breaking first
Yeah, I charge my HD2 multiple times in a day because I use it so much.
Wonder how long my phone will last. Got it brand new a couple of months ago
ive had my hd2 since it came out in nov09 and its been charged every single night bar probably about 2 weeks worth of time, and never had an issue with anything going wrong
silverwind said:
Thanks for enlighten us
I have some bad blocks in my HD2, I always think that it is due to my excessive flashing habit. I flash almost roms avaiilable since I join xda
Now, it taken its toll. SOme nand android roms fails to flash and boot due to this bad blocks.
However, I still can flash wm 6.5 and runing SD Android without any problems
Cheers
Click to expand...
Click to collapse
hey, I have a HD2 with bad memory NAND blocks and know my HD2 will not boot up but do you have any suggestions because i really do like the phone but it just won't boot?
kawazaki said:
It's not how many times you flash it, It's how well you do the flash and how good the files are.
So if you read before you flash and you flash trusted files your device shall live for decades .
But if you always ignore the "Warnings" and flash untrusted files carelessly, your device may not see the day light of tomorrow .
-By trusted files I mean files compatible with your device and from a known developer
-By reading I mean reading thoroughly the entire post, and check the replies as well as they always contain first known issues .
- I remember a guy who has just bought his HD2, he wanted to install a custom ROM, he was told to upgrade his radio, after he did his device wouldn't boot. It turned out he flashed the incompatible radio for a Tmous .
Click to expand...
Click to collapse
Is there anything you can do for that because i think i did that to my HD2 if you plz message me back because my HD2 wont boot and i really do need this phone so if you can help plz do?
If your getting bad blocks and its giving you headaches and you have zero issues with the ipl/spl then just switch to SD android builds
they might work a tiny bit slower but at least you can still use the phone happily.
My phones almost a year old now, but i did not use it for nearly 4 months coz I got a desire. Sold that on ebay and gone back to the HD2 when magldr came out. I go by 2 simple rules...
Dont flash the radio/spl if you have no bloody reason to. there's only 1 good radio and that's the normal 2.15 HSPL. the fact that those NAND blocks are so critical means dont touch unless its majorly important to do so.
Secondly, make sure you dont let any rogue processes in android go into a massive file write fit of frenzy, and disable logging in apps that log allot to internal NAND or change it to log to the SD Card.
More often your touch input will fail, or those buttons will fail.
Dont worry about abusing the daylight out of the battery, its worth $1 and can be replaced anytime, but don't abuse that precious usb port.... treat it well and blow some air into it once in a while.
1 more tip, dont use car chargers they dont filter well and the last thing you need is a high voltage surge going into the phone, instead what i did is buy a sinewave invertor and then run an ac charger from that and i get the added benefit of sometimes bring a power board and can run the kids dvd player indefinetly and charge other phones... laptops.... GPS Navman.
HELP my Samsung Omnia 7 GT-I8700, works only in download mode (power + camera button + volume up) if I try to do (power + volume down + camera button) I see the word format so fast. - And restarts with the message that flashes omnia7 samsung. I tried to put many different rom but when making the first reboot hangs forever ....
thanks in advance
probably memory problem that the some Omnias are known to experience, send it to Samsung for a warranty repair.
I'm afraid that You have a "dead boot". I don't know how You did it, but for today nobody knows how to repir it. Even using a RIFF Box... So it could be a difficult mission. Tell us what have You done with it?
Warranty is the ONLY solution. eMMC chip fried.
htc9420 said:
Warranty is the ONLY solution. eMMC chip fried.
Click to expand...
Click to collapse
hello, can you write something more about that?
a_r_e_n_a said:
hello, can you write something more about that?
Click to expand...
Click to collapse
has restarted by itself, has remained with the words that flashed omnia 7. -
I'll bring in assitance, I think it's the only way.
It is common with sammy's memory chips to die out of the blue. Most of the times the EMMC chip just gives and it's done, sometimes the the internal mem hangs. There's no way to recover. I suspect it's HW issue induced by faulty Sammy drivers, it's been reported to affect some Android phones running leaked ICS also.
Also, maybe it's a downfall of the way WP7 handles physical mem. It only occurs when flashing or updating through hard reset. It's the eMMc that is only used then to format, partition and so on. There were a lot of hardbrick on the first WP7 update so all leads to Sammy.
Sadly, the only option is MB swap. As the Omnia7 is a late 2010 model, all the phones are covered by warranty. Just call a SC and when they ask you about the receipt, tell them that they should consider the date of mfg as the date when the device was made-they know that by the IMEI.
htc9420 said:
It is common with sammy's memory chips to die out of the blue. Most of the times the EMMC chip just gives and it's done, sometimes the the internal mem hangs. There's no way to recover. I suspect it's HW issue induced by faulty Sammy drivers, it's been reported to affect some Android phones running leaked ICS also.
Also, maybe it's a downfall of the way WP7 handles physical mem. It only occurs when flashing or updating through hard reset. It's the eMMc that is only used then to format, partition and so on. There were a lot of hardbrick on the first WP7 update so all leads to Sammy.
Sadly, the only option is MB swap. As the Omnia7 is a late 2010 model, all the phones are covered by warranty. Just call a SC and when they ask you about the receipt, tell them that they should consider the date of mfg as the date when the device was made-they know that by the IMEI.
Click to expand...
Click to collapse
I have asked for the assistance received, without the receipt I have to pay 150 €.
I bought on ebay omnia 7 with a broken glass € 50, I replaced the glass with mine. I have a 7 omnia omnia that works and a 7 by throwing with broken glass and faulty memory.
Wasser Marshmallow ROM SDCard version R89 2G/16G
Ok heres an image https://www.dropbox.com/s/g3zmf8zo6z...K3288.rar?dl=0 to use for Beelink R89. This works on mine which is a pre production model 2G/16G . This image has been made with HDD Raw Copy then compressed with WinRar.
Steps
1. Download HDD Raw Copy http://hddguru.com/software/HDD-Raw-...y1.10Setup.exe
2. Extract Rar archive
3. Open HDD Raw Copy
4. Double click File, locate and chose SDWasser IMGC click continue
5. Choose SDCard Reader then click start
6. Once writings finished put sd in android box and power up
******First boot may take a while but let it settle down before judging give it 10mins from homescreen before rebooting then see what performance is like*******
Dont thank me thank the ones that make it work I'm just a bodger
So having messed with tons of android devices trying to find the holy grail I found realistically the SOC's usually are fine and within spec ( except s905 which has never run @2Ghz no matter what device its in as amlogic has set the chips at 1.56ghz which came to light about a month ago from odroid c2 users so all s905 devices wrongly advertised). The issue time and time again has been the crap components that have be used with the SOC. Heres an example I became a beta tester for the beekink R89 and having had a tronsmart MK908II with crap faulty reclaimed foresee nand flash memory never worked right until I started using an Sdcard to run android from which made this TV stick almost perfect (best device out of them all once running from SD), I asked beelink to NOT use foresee nands and on receiving my R89 discovered it did indeed have foresee nand chips which cause it to stutter and stop all the time. So what was the point of carrying on beta testing the product which is crippled hardware wise and unusable. Nearly 2 year later I picked the box up again and put Marshmallow on a sandisk 16GB U3 sdcard. I've only run it for about 5 hours but its like lightening scores over 57000 on antutu suffers no microskips. So the SOC does do its job as the card reader is built into the SOC and not something beelink has added. Its probably the best android device I've got now and I'm really pleased with it. So if you struggle with these devices try and run of SD but don't use any old **** use a sandisk U3 card or a Samsung Evo SD trust me all SD cards are not the same transcend and Kingston have big compatibility issues I'll show any one my pile of different makes I've tried and won't touch any other brands in future.
May edit more later........
LawlessPPC
Sent from my MotoG3 using Tapatalk29 minutes ago
Ok heres an image https://www.dropbox.com/s/g3zmf8zo6z...K3288.rar?dl=0 to use for Beelink R89. This works on mine which is a pre production model 2G/16G . This image has been made with HDD Raw Copy then compressed with WinRar.
Steps
1. Download HDD Raw Copy http://hddguru.com/software/HDD-Raw-...y1.10Setup.exe
2. Extract Rar archive
3. Open HDD Raw Copy
4. Double click File, locate and chose SDWasser IMGC click continue
5. Choose SDCard Reader then click start
6. Once writings finished put sd in android box and power up
******First boot may take a while but let it settle down before judging give it 10mins from homescreen before rebooting then see what performance is like*******
Dont thank me thank the ones that make it work I'm just a bodger
So having messed with tons of android devices trying to find the holy grail I found realistically the SOC's usually are fine and within spec ( except s905 which has never run @2Ghz no matter what device its in as amlogic has set the chips at 1.56ghz which came to light about a month ago from odroid c2 users so all s905 devices wrongly advertised). The issue time and time again has been the crap components that have be used with the SOC. Heres an example I became a beta tester for the beekink R89 and having had a tronsmart MK908II with crap faulty reclaimed foresee nand flash memory never worked right until I started using an Sdcard to run android from which made this TV stick almost perfect (best device out of them all once running from SD), I asked beelink to NOT use foresee nands and on receiving my R89 discovered it did indeed have foresee nand chips which cause it to stutter and stop all the time. So what was the point of carrying on beta testing the product which is crippled hardware wise and unusable. Nearly 2 year later I picked the box up again and put Marshmallow on a sandisk 16GB U3 sdcard. I've only run it for about 5 hours but its like lightening scores over 57000 on antutu suffers no microskips. So the SOC does do its job as the card reader is built into the SOC and not something beelink has added. Its probably the best android device I've got now and I'm really pleased with it. So if you struggle with these devices try and run of SD but don't use any old **** use a sandisk U3 card or a Samsung Evo SD trust me all SD cards are not the same transcend and Kingston have big compatibility issues I'll show any one my pile of different makes I've tried and won't touch any other brands in future.
May edit more later........
LawlessPPC
Sent from my MotoG3 using Tapatalk
Help Please
Recently my UBOX4k R89 (same board as BeelinkR89) stopped booting wassers Lollipop build and would stick athe Wasser spinning logo. I tried to run this image from an SD card, following your instructions but it keeps trying to boot from the onboard storage. I tried to reflash to Beelinks image and to wassers onboard Marrshmallow build, same ressult, stuck on boot screen.
I wonder if its a hardware fault or just that something in the partitioning is wrong. I am a IT guy but new to nand flasing. I am wondering if there is any diagnostic tools for the R89 that can narrow my troubleshooting options.
Any suggestions?