Develop Bugs

Will phone manufacturers even listen and get it right ?

Hi
this is basically going to be a rant and rave but hopefully a constuctive one
For years i have had smartphones, mainly WM but have strayed to Symbian once and now Android with the Desire
I remember upgrading from the TYTN to the TYTNII and HTC not supplying the drivers we had no proper divx playback and this continued onto the Touch HD which is pretty much why i dediced to go to Android.
Now i have the Desire which i must admit is a very good phone but the storage spce is laughable even with Froyo update which helps a bit it's pathetic
Now i cant wholly blame HTC for this as it's the Android OS that is causing the issue but having more Internal Memory would help.
Strange that the reason for Android not having all data on the sd was to help with piracy and i must admit i have been very conciencous through the years and always bought what i used but now googles policy is forcing me the other way, why pay for apps that i have to uninstall so i can install something else.
Windows Mobile has allowed SD card installs since my first 2003 device, Android has taken a massive step back in my opinion. So much for the 1000's of apps on the android market, it does not say you can only browse them but dont install many as your phone will grind to a halt.
so not so long ago i thought i would get rid of the desire and try another android device only with more internal mem.
i looked at the X10 , looks a good phone but it's still on 1.6 and the promised updates are still just promises.
the Galaxy s looks excellent and has loads of space but it looking around it seems to have quite a few issues with lagging and the GPS issues.
So i thought about looking at the Desire HD but i have problems with the Battery life on the Desire and as the HD battery is smaller there is no way i could live with it.
It seems as if the Maunfacturers are just happy to churn these things out without too much thought , maybe it's cause they always want us to upgrade but just think if one actually made a phone that does what is is supposed to do and do them well they may end up with making a killing.
Rant mode over apart from now that i dont use sense i still cant find a 4x4 rss widget

machmandp said:
Hi
this is basically going to be a rant and rave but hopefully a constuctive one
For years i have had smartphones, mainly WM but have strayed to Symbian once and now Android with the Desire
I remember upgrading from the TYTN to the TYTNII and HTC not supplying the drivers we had no proper divx playback and this continued onto the Touch HD which is pretty much why i dediced to go to Android.
Now i have the Desire which i must admit is a very good phone but the storage spce is laughable even with Froyo update which helps a bit it's pathetic
Now i cant wholly blame HTC for this as it's the Android OS that is causing the issue but having more Internal Memory would help.
Strange that the reason for Android not having all data on the sd was to help with piracy and i must admit i have been very conciencous through the years and always bought what i used but now googles policy is forcing me the other way, why pay for apps that i have to uninstall so i can install something else.
Windows Mobile has allowed SD card installs since my first 2003 device, Android has taken a massive step back in my opinion. So much for the 1000's of apps on the android market, it does not say you can only browse them but dont install many as your phone will grind to a halt.
so not so long ago i thought i would get rid of the desire and try another android device only with more internal mem.
i looked at the X10 , looks a good phone but it's still on 1.6 and the promised updates are still just promises.
the Galaxy s looks excellent and has loads of space but it looking around it seems to have quite a few issues with lagging and the GPS issues.
So i thought about looking at the Desire HD but i have problems with the Battery life on the Desire and as the HD battery is smaller there is no way i could live with it.
It seems as if the Maunfacturers are just happy to churn these things out without too much thought , maybe it's cause they always want us to upgrade but just think if one actually made a phone that does what is is supposed to do and do them well they may end up with making a killing.
Rant mode over apart from now that i dont use sense i still cant find a 4x4 rss widget
Click to expand...
Click to collapse
FYI, the battery is smaller on the desire HD because the 2nd generation snapdragon it has, has much improved battery performance so its not needed

sigh...here we go again...root your device, root your device
you are willing to go as far as buying a new handset?? but your not willing to root?
root your device, install A2SD+ and SD speed fix and you will never look back, it runs flawless
if you cant be bothered learning how, ask someone to do it for you
Tech magazines are choosing the HTC desire as phone as the year as one of the most balanced android phones available
issues like app storage, music/video stutter (due to slow SD read) and even gaming performance can be fixed or improved by rooting your device

hamdir said:
sigh...here we go again...root your device, root your device
you are willing to go as far as buying a new handset?? but your not willing to root?
root your device, install A2SD+ and SD speed fix and you will never look back, it runs flawless
if you cant be bothered learning how, ask someone to do it for you
Tech magazines are choosing the HTC desire as phone as the year as one of the most balanced android phones available
issues like app storage, music/video stutter (due to slow SD read) and even gaming performance can be fixed or improved by rooting your device
Click to expand...
Click to collapse
The point is you shouldn't HAVE to root your Desire. Look at the Desire HD - 1.5GB of internal space. HTC realised they made a mistake and have now corrected this.
Just cause A2SD is available if you root some people don't WANT to root as it's shouldn't have been needed. For some warranty is actually important

hi again
I dont want to start arguments but as EddyOS wrote why should we have to root ?
to get the desire running well you have to invalidate the warranty does not sound too good.
anyhow i am rooted and use the Move2SDEnabler to move as many apps as possible but kept the stock rom as no orange rom is available as yet in case of warranty issues.
but some cannot be moved and i have 22mb free
a brief list of some of the app sizes i have
Google Maps 8.81mb
Swype 6.03mb
paypal 4.79mb
Ndrive 4.39mb
Gmail 4.1mb
Folder Org 3.88mb
launcher Pro 3.73mb
titanium Backup 2.88mb
Moblox 2.88
beautiful widgets 2.11mb
angry birds 1.92mb
just with these thats 45mb i obviously have more apps installed but as each one takes up anywhere from a few k to 2 mb then how are we expected to be able to install a good amount apps
can i do without any of the above maybe but the point is why should i have to - i purchased them and dont forget the main advertising points about Android are the Market and Customising the Launcher with Widgets.
And as regards to the desire having been chosen as the best phone i wonder how many of the reviewers actually use the phone daily or is it based on a few days usage.
I was under the impression that how i use Froyo Apps2SD was pretty much the same as Apps2SD+ but if you now different then please point me in the right direction
Thanks

A2SD in FroYo only moves the app itself and not the data accociated with it. This only works on apps that have been enabled by the developer to be moved. A2SD+ differs by actually using the EXT3 partition on the SD card as internal memory so all the app data is stored on the SD card (bar some data which has to remain on the device).
HTC have since addressed things with their new handsets by giving them a LOT more internal memory so this should be a thing of the past BUT it doesn't help Desire owners who, like you, can't root as there isn't a stock RUU to revert to for warranty issues (which is a whole different matter and why I only get generic handsets). The only way to incrase memory is to root

machmandp said:
i am rooted and use the Move2SDEnabler to move as many apps as possible but kept the stock rom as no orange rom is available as yet in case of warranty issues.
Click to expand...
Click to collapse
You already have a 'void' warranty because you have root, you may aswell go the whole 9 yards and flash a custom rom. just make a nandroid backup of your current rom so you can go back to it if the worst happens.
Having a void warranty never stopped orange from swapping my phone.
I do agree that you shouldn't have to root your phone to make it work, but that's just the way it is

EddyOS said:
A2SD in FroYo only moves the app itself and not the data accociated with it. This only works on apps that have been enabled by the developer to be moved. A2SD+ differs by actually using the EXT3 partition on the SD card as internal memory so all the app data is stored on the SD card (bar some data which has to remain on the device).
Click to expand...
Click to collapse
Not entirely correct!
If you ModInstallLocation (which does not require root) you can force most apps to move to SD with FROYO A2SD - as far as I'm aware the exceptions to this have explicity disallowed this.
The main difference between FROYO A2SD and A2SD+ is that A2SD+ relocates the Dalvik cache to SD. Both methods leave /data/data on the device which in the case of some apps (e.g. Google Earth) can be quite substantial.
Personally I use FROYO A2SD, but I've repartitioned to reclaim space from /system and I use Fusecompress to compression the Dalvik cache.
To the OP, you can argue that this is an Android OS issue, but in my opinion this was always an issue with poorly specified hardware rather than the Oscar itself.
My Galaxy Tab has 2GB set aside for applications and the Desire Z/HD have 1.5GB, which rather renders any form of A2SD obsolete.
Regards,
Dave

Well,if you manage to break your phone somehow make sure you break it badly enough for rendering them unable to detect if you have it rooted!

mercianary said:
You already have a 'void' warranty because you have root, you may aswell go the whole 9 yards and flash a custom rom. just make a nandroid backup of your current rom so you can go back to it if the worst happens.
Having a void warranty never stopped orange from swapping my phone.
I do agree that you shouldn't have to root your phone to make it work, but that's just the way it is
Click to expand...
Click to collapse
But you can remove the root right?
Because my Desire started up with the "rebootloop by itself" issue a month ago while I had LeeDroid 2.2x running, and so I removed root by installing a RUU and then sent it away for service like yesterday.
And then they can't void the warranty then right? RIGHT??? :S

Yes but the point is that Orange (the OPs operator) don't have an RUU so you can't do that

EddyOS said:
Yes but the point is that Orange (the OPs operator) don't have an RUU so you can't do that
Click to expand...
Click to collapse
Oh, didn't think about that at all.
Hmm, well then he does have some valid complaints. My biggest problem with the unrooted Desire is the internal memory, and I certainly didn't have any idea how small it was prior to purchase and just took for granted that you could store apps on the SD.

EddyOS said:
Yes but the point is that Orange (the OPs operator) don't have an RUU so you can't do that
Click to expand...
Click to collapse
Yep that's a big problem for me
As i said i have root but i thought (right or wrong) that if i ever have a problem there is more chance of the service centre not spotting anything if i still have the stock orange rom.
Also when i looked into flashing roms i'm sure that there was an issue with the Orange radio that caused massive problems and that really put me off from doing that.
I must admit i now have 19mb free and have had to delete some apps today after installing the flash update (Another 10mb) and it seems that updates are slowly eating all of the memory and surely HTC must have known this was going to be a problem.
Still i'll now try to look into maybe flashing a rom with APPS2SD+ and see if it's ok to do. i'll also hope for an Orange RUU to be leaked soon
Thanks all

This is what I'd do...
Remove all apps from the phone (uninstall them). And then reboot into recovery. Do a backup so you can revert back to it should you need to send it in (they may not realise you're rooted) but then you can go to a custom ROM using A2SD+ and see how you get on

EddyOS said:
This is what I'd do...
Remove all apps from the phone (uninstall them). And then reboot into recovery. Do a backup so you can revert back to it should you need to send it in (they may not realise you're rooted) but then you can go to a custom ROM using A2SD+ and see how you get on
Click to expand...
Click to collapse
thanks
sounds like my only choice to avoid the low space
just need to double check the Orange radio thing first
Thanks all

The newer radios should work OK, if not you can use the radio you're on at present assuming you're on Android 2.2 at the moment (albeit the Orange version) - flashing a custom won't touch the radio unless it's included in the ROM file

The radio hasn't been a problem for a while. The newer radios wont lock your device.
My first orange desire was locked by a radio update. I had to fix it with an unlock code.
My second orange desire (warranty replacement) was not locked when I flashed the most recent radio.

Excellent thanks
One more quick question if I may
In your experience would I be better getting a fast mem card as I only have class 2 at the moment
Sent from my HTC Desire

I use a class 2 16GB card and have no issues

hi
well i finally got round to flashing a new rom
went for the leedroid in the end with A2SD+
I had a few issues but read up and worked around them although i read about a gold card but never created one so i hope i'm not setting myself up for a fall without it.
anyhow i'm glad i did it with loads of apps installed i still have 85mb free and nowhere near filled up my 1gb ext3 partition
thanks for the advice all

Combining FRX03 with Neopeek FRG83.R5 with working Bluetooth ?

Dear Reefermattness and arrrghhh !
I apologize for making a new thread but I just want have your attention on the Neopeek Release for Rhodium.
In this forum stays that in FRG83.R5 release
http://www.neopeek.com/en/forum/Android-ROMs/2183-ROM-FRG83-Build-Froyo221-05-11-2010
Bluetooth IS WORKING !
I have no idea what this release can, but I saw its structure. Basically EXT2 Partition for Neopeek is the same thing that system.ext2 file for FRX03 !
And in andoidinstall.tar.gz file is the same stuff as in system.ext2 and roofts.img together.
Why we just not pick the working Bluetooth "driver-package-what-ever" from Neopeek and combine it with FRX03 ? I could do it by my self, but I don't have deep system structure know-how.
I must say that FRX03 is lot easier to handle (getting ready, install, edit etc) thats why I'd prefer working with it as with Neopeek.
And besides I just reached almost 8 hrs of working time with one charge on it with new kernel and startup change. Thats why I want to improve it. Can you help me to understand the structure of driver packages for BT ?
Thank you
-------------------------------------
----------------
EDIT:
Here it is, a repack of SuperFroyo in system.ext2 file.
http://narod.ru/disk/27385762000/system.zip.html
I didn't test it yet. But if some one want to try out - please download and report back !

d0nate110 said:
Dear Reefermattness and arrrghhh !
I apologize for making a new thread but I just want have your attention on the Neopeek Release for Rhodium.
In this forum stays that in FRG83.R5 release
http://www.neopeek.com/en/forum/Android-ROMs/2183-ROM-FRG83-Build-Froyo221-05-11-2010
Bluetooth IS WORKING !
I have no idea what this release can, but I saw its structure. Basically EXT2 Partition for Neopeek is the same thing that system.ext2 file for FRX03 !
And in andoidinstall.tar.gz file is the same stuff as in system.ext2 and roofts.img together.
Why we just not pick the working Bluetooth "driver-package-what-ever" from Neopeek and combine it with FRX03 ? I could do it by my self, but I don't have deep system structure know-how.
I must say that FRX03 is lot easier to handle (getting ready, install, edit etc) thats why I'd prefer working with it as with Neopeek.
And besides I just reached almost 8 hrs of working time with one charge on it with new kernel and startup change. Thats why I want to improve it. Can you help me to understand the structure of driver packages for BT ?
Thank you
Click to expand...
Click to collapse
1) as far as I understand Neopeek uses large parts of Xdandroid projects, starting from the kernels/rootfs. This is not hidden/secret, so he and xda devs may know each other pretty well.
Therefore I can't understand how he can have bluetooth working and Xdandroid not.
then ...
2) maybe he shares branches of code and patches with our devs, but while our devs decided that the code to make bluetooth working is still too buggy, he could have decided to shoot it in for good. In fact reading comments on the thread you posted you will see that at the end the people crying for not-working BT are a lot ...

I'd be interested to see if BT works fully. I've seen some where they scream that BT works, but then when they actually try to use BT... it fails. So if it pairs and nothing else, that's what state our build is in as well.

I just installed it, on a blank 2Gb I had spare.
At start it's quite a pain in the arse ...
cmdline was a little different, I just set correct keyboard.
But I immediately put the latest kernel (24.11.2010). Both in installer and main.
Much faster than Xdandroid. Much faster at boot, much snappier in launcher etc., but this may be related also to the age (of the FAT32 file system) of the other SD I use for Xdandroid. Will format it and see what happens swapping.
But then, when it went to sleep it just crashed.
I tampered with the startup, added pmsleepmode=2, this worked, tried =1 and works quite well.
As I expected, BT doesn't work on my RHOD100.
This neopeek build comes nearly all from xdandroid, so it seems it's not as up to date.
But while that guy takes most of development from XDA, he must work a lot on tweaks, therefore XDA should take something back ...
I'll try cleaning the other SD and check what happens.

Installed on extra card. Rhodium 400 . It is fast. Boots quicker. The initial setup screens are very friendly. Power off and other buttons work more like winmo. Bluetooth will not turn on. Phone works. Data does not work. Have to use WiFi for data. USB while in Android does work (sweet). Key board backlighting not working. I am going to reinstall with bluetooth enabled initially in winmo.

Neopeek SuperFroyo Repack into system.ext2
arrrghhh said:
I'd be interested to see if BT works fully. I've seen some where they scream that BT works, but then when they actually try to use BT... it fails. So if it pairs and nothing else, that's what state our build is in as well.
Click to expand...
Click to collapse
Here it is, a repack of SuperFroyo in system.ext2 file.
http://narod.ru/disk/27385762000/system.zip.html
I didn't test it yet. But if some one want to try out - please download and report back !

reinstalled Bluetooth not working. Rhodium 400
Only things that could make improvements to XDA android are Speaker phone is working. USB in android does work. Buttons function as they should. It works with SIM card installed. Speed. Boots faster. Screen adjusts to right profile on start lockscreen.USB headset works without line in startup.
Still not working
Data does work but have to manually set APN. Headset does not work ( Does work with line in Startup and calling during boot). Problems with the market downloading.
Does work tethering. pretty much everything
One nice thing is they have a seperate install folder so if your system is corrupted you just reinstall with file manager in winmo. It reformats the ext2 partition on the card. I assume the sizing of partition is in place of the sizing the data.img file on the card.
Being open source borrowing a few items should not be considered crossing a line.

d0nate110 said:
Here it is, a repack of SuperFroyo in system.ext2 file.
http://narod.ru/disk/27385762000/system.zip.html
I didn't test it yet. But if some one want to try out - please download and report back !
Click to expand...
Click to collapse
wait a minute.. you didnt test it and are spreading it like wild fire ?
before you cry wolf, at least pretend you saw one ..

First Full Day Of Testing
[ACL] said:
wait a minute.. you didnt test it and are spreading it like wild fire ?
before you cry wolf, at least pretend you saw one ..
Click to expand...
Click to collapse
I've tested this strange build a whole day today... I must say...I'm confused...
First of all I charged my battery to full 100% in WinMo. Then I've just replaced old system.ext2 with this one (my other files incl. kernel were untouched) and booted a clean Haret and saw, that this Android Learning Demo just didn't want to go on if I taped on it...
My device was locked and I must reboot it...then I delete my data.img file and tried again... success - SuperFroyo booted well.
- Bluetooth doesn't work as pessimistically expected
Other stuff works same like in our Froyo Reference.
- flash 10.1, loudspeaker, camera, usb connection and headphones don't work
- sleep_mode=1, wifi, phone, wake up on call and Market are working.
But Battery life was little better according to JuicePlotter... and I had a feeling, that all the system works little bit faster... I don't know if it is just placebo effect, but I thing its true...
I'll keep testing it for another 3-5 days and report back... and BTW you can test it too.

d0nate110 said:
I've tested this strange build a whole day today... I must say...I'm confused...
First of all I charged my battery to full 100% in WinMo. Then I've just replaced old system.ext2 with this one (my other files incl. kernel were untouched) and booted a clean Haret and saw, that this Android Learning Demo just didn't want to go on if I taped on it...
My device was locked and I must reboot it...then I delete my data.img file and tried again... success - SuperFroyo booted well.
- Bluetooth doesn't work as pessimistically expected
Other stuff works same like in our Froyo Reference.
- flash 10.1, loudspeaker, camera, usb connection and headphones don't work
- sleep_mode=1, wifi, phone, wake up on call and Market are working.
But Battery life was little better according to JuicePlotter... and I had a feeling, that all the system works little bit faster... I don't know if it is just placebo effect, but I thing its true...
I'll keep testing it for another 3-5 days and report back... and BTW you can test it too.
Click to expand...
Click to collapse
I'm on nand, so i cant run that abomination. However i did run the real cyanogen and it was a lil faster. But it took too many changes to the rootfs to get it to run.. i havent tried it since..
Also im not sure why neopeek isnt using our rootfs structure so you can swap the system.imgs easier .. maybe you should ask him

too buggy things would work then stop working. I could plug in a usb headset have it work in a call or music unplug it then plug it back in and it does not work. Many other things like that. Same with the 3.5 jack trick it would work sometimes then sometimes not. If u left it stock it works great and is very fast. Diamond users were happy. I have a diamond that I will try it on sometime next week, but it is not good for rhodium. It did something to the usb on my Rhodium in winmo would not work so gave me a chance to jack in energy rom like that so far.

[ACL] said:
I'm on nand, so i cant run that abomination. However i did run the real cyanogen and it was a lil faster. But it took too many changes to the rootfs to get it to run.. i havent tried it since..
Also im not sure why neopeek isnt using our rootfs structure so you can swap the system.imgs easier .. maybe you should ask him
Click to expand...
Click to collapse
Sorry for silly question, but what do you mean with "being on nand"?
And, lol, why abomination!?!?!?
It's clearly taken from FRX02 Xdandroid build, but tweaked to be more speedy.
These tweaks are something that Xdandroid should port back to main project.
I have only one crash a day with Neopeek's FRG83.R5, while Xdandroid FRX03 is not only slower on my TP2 rhod100, even with around 100Mb ram free, but keeps slowing down even more while using, so that I have to restart.
In the last week this led to process ".acore" crashing almost immediately after boot, with no solution known to me except reinstalling.
That's once a day.
Neopeek did this only once.
Still have to understand what leads to ".acore" process chain crashes.
I would prefer to use Xdandroid FRX03, because it's more up to date and standard compliant, but, strangely, it's not as stable as Neopeek's FRG83, on my phone.
Cheers.
EDIT:
uh, oh, d0nate, I think we are messing it a little bit here. I am testing FRG83.R5, not SuperFroyo.
They are 2 different builds.
What are you effectively testing?

Sorry about that
sad0felix said:
EDIT:
uh, oh, d0nate, I think we are messing it a little bit here. I am testing FRG83.R5, not SuperFroyo.
They are 2 different builds.
What are you effectively testing?
Click to expand...
Click to collapse
First of all I AM NOT Donate - I'm donatello written with numbers
I don't want any donations and hate money
Second I apologize, but I can't implement FRG83.R5 to use without formating my SD-card thats why I use a SuperFroyo. The member DmK75 gave me this link to system.ext2 file with SuperFroyo release in it...
I try though to repack FRG83.R5 also in system.ext2 file later... I just don't have the know-how yet...

sad0felix said:
Sorry for silly question, but what do you mean with "being on nand"?
And, lol, why abomination!?!?!?
It's clearly taken from FRX02 Xdandroid build, but tweaked to be more speedy.
These tweaks are something that Xdandroid should port back to main project.
I have only one crash a day with Neopeek's FRG83.R5, while Xdandroid FRX03 is not only slower on my TP2 rhod100, even with around 100Mb ram free, but keeps slowing down even more while using, so that I have to restart.
In the last week this led to process ".acore" crashing almost immediately after boot, with no solution known to me except reinstalling.
That's once a day.
Neopeek did this only once.
Still have to understand what leads to ".acore" process chain crashes.
I would prefer to use Xdandroid FRX03, because it's more up to date and standard compliant, but, strangely, it's not as stable as Neopeek's FRG83, on my phone.
Cheers.
EDIT:
uh, oh, d0nate, I think we are messing it a little bit here. I am testing FRG83.R5, not SuperFroyo.
They are 2 different builds.
What are you effectively testing?
Click to expand...
Click to collapse
Ahh you poor soul.. nand meaning i no longer have wince so i cant run his installer. Abomination is a strong word.. so i take it back . But i do think it's wicked and it's not a child of xdandroid like you think. The main chunk of the project comes from cyanogen. The only parts that were pillaged from xdandroid appear to be some of the roofs files (including the hardware libs). And of course, our kernel runs the whole show.
Now why would i run some hacked up version if i can run cyanogen directly? Plus cyanogen has everything open, so we can easy work and modify it as we need. I have not seen anything shared by neopeek, so i dont feel its fair to the xdandroid team since we pretty much share everything.
If it's stable for you.. awesome.. maybe there is future for it.

[ACL] said:
Ahh you poor soul.. nand meaning i no longer have wince so i cant run his installer. Abomination is a strong word.. so i take it back . But i do think it's wicked and it's not a child of xdandroid like you think. The main chunk of the project comes from cyanogen. The only parts that were pillaged from xdandroid appear to be some of the roofs files (including the hardware libs). And of course, our kernel runs the whole show.
Now why would i run some hacked up version if i can run cyanogen directly? Plus cyanogen has everything open, so we can easy work and modify it as we need. I have not seen anything shared by neopeek, so i dont feel its fair to the xdandroid team since we pretty much share everything.
If it's stable for you.. awesome.. maybe there is future for it.
Click to expand...
Click to collapse
Woah ... I am feeling soooo noob ... dang you!!!
Since I wrote my previous post my knowledge grew about ten times ... from 0.001% to 0.01%, so now I can see what you mean about Cyanogen and all the rest.
I know it's everything but a good excuse, but please notice that I got to Android just in the form of Xdandroid, and only in the last few weeks.
So I am learning. Maybe faster than mean people, still much slower than hardcores like you or the other devs.
----------------
In the meanwhile I reverted back to FRX03.
Mainly because of stabilities (better, instabilities are regular so that can be forecasted and behaviors provoking them can be avoided with good success rate).
Still I think that maybe (and I cap it, MAYBE) Xdandroid could (I don't say should, it would be excessive) benefit from the Neopeek/Cyanogen "thing".
You know, like when you have a crate of stuff, you dive hands in it and choose and pick up just the good things/those you like.
I just dream a Xdandroid snappy like Neopeek's whatever build (I tried 2).
... the speed ... the speed .... (put here Marlon Brando's voice in Platoon, when he repeats "the horror" ... ).
Cheers!
EDIT:
I fear that you did it all by yourself, but in any case I ask you.
Is there any public documentation about going nand? What are the advantages?
You put a thermite in my left ear, you know?!?!?!

Here's the PPCG thread on NAND boot testing. Not for the faint of heart...

sad0felix said:
Woah ... I am feeling soooo noob ... dang you!!!
Since I wrote my previous post my knowledge grew about ten times ... from 0.001% to 0.01%, so now I can see what you mean about Cyanogen and all the rest.
I know it's everything but a good excuse, but please notice that I got to Android just in the form of Xdandroid, and only in the last few weeks.
So I am learning. Maybe faster than mean people, still much slower than hardcores like you or the other devs.
----------------
In the meanwhile I reverted back to FRX03.
Mainly because of stabilities (better, instabilities are regular so that can be forecasted and behaviors provoking them can be avoided with good success rate).
Still I think that maybe (and I cap it, MAYBE) Xdandroid could (I don't say should, it would be excessive) benefit from the Neopeek/Cyanogen "thing".
You know, like when you have a crate of stuff, you dive hands in it and choose and pick up just the good things/those you like.
I just dream a Xdandroid snappy like Neopeek's whatever build (I tried 2).
... the speed ... the speed .... (put here Marlon Brando's voice in Platoon, when he repeats "the horror" ... ).
Cheers!
EDIT:
I fear that you did it all by yourself, but in any case I ask you.
Is there any public documentation about going nand? What are the advantages?
You put a thermite in my left ear, you know?!?!?!
Click to expand...
Click to collapse
nand is for the brave.. so if you are just starting. then stay away since we already had a brick happen. I also corrupted something myself so it can get nasty. Once we stabilize it will get better. The main advantage is that you no longer have windows. lol.. but the disadvantage is that you dont have windows to fall back on. It also lets us develop as if the phone would be native to android. Believe it or not but wince does alot of the dirty work for us. So the nand project lets us recreate all that ourselves.
Cyanogen is just a different animal. Xdandroid is based of pure google code as it was meant to be. It also lets us modify it for our devices that were never meant to have android. Cyanogen only supports devices that already came with android. You can modify it to run on other devices, but the main builds themselves are for specific devices. Xdandroid supports all with just 1 build. We forget sometimes about our other winmo htc brethren like topaz and blacstone. But they need a build too.. .
If you are really interested in this, you can clone both codes and compare just how different we are. If you find something you think will benefit, try it out and see what happens. Gotta love opensource.

[ACL] said:
nand is for the brave.. so if you are just starting. then stay away since we already had a brick happen. I also corrupted something myself so it can get nasty. Once we stabilize it will get better. The main advantage is that you no longer have windows. lol.. but the disadvantage is that you dont have windows to fall back on. It also lets us develop as if the phone would be native to android. Believe it or not but wince does alot of the dirty work for us. So the nand project lets us recreate all that ourselves.
Click to expand...
Click to collapse
Hep, I am just a curious guy.
One of those many that want to put their nose everywhere, but also one of the few that:
a) most of the times will need to read the guide just once (if guide isn't enough there are FAQs and Google),
b) will follow instructions easily because normally understands what they mean/what they are for
c) will never give it up until success
d) will never come to the forum writing: "I have a phonez, tried to put some android on it, doesn't work HELP1!!1!!1!"
Moreover, my TP2 is just 6 months old, is a gift, I use it for work, so to not void the warranty I didn't even install HardSPL on it.
So do not worry.
I am just curious to read how you can do it.
But will not die if I don't know yet
Cyanogen is just a different animal. Xdandroid is based of pure google code as it was meant to be. It also lets us modify it for our devices that were never meant to have android. Cyanogen only supports devices that already came with android. You can modify it to run on other devices, but the main builds themselves are for specific devices. Xdandroid supports all with just 1 build. We forget sometimes about our other winmo htc brethren like topaz and blacstone. But they need a build too.. .
If you are really interested in this, you can clone both codes and compare just how different we are. If you find something you think will benefit, try it out and see what happens. Gotta love opensource.
Click to expand...
Click to collapse
Basically you are suggesting me that all the (amazing) speed of Neopeek's builds comes just from using direct EXT/SWAP partitions on SD.
So, is there anyone trying to build a Xdandroid with EXT/SWAP structure?

sad0felix said:
Basically you are suggesting me that all the (amazing) speed of Neopeek's builds comes just from using direct EXT/SWAP partitions on SD.
So, is there anyone trying to build a Xdandroid with EXT/SWAP structure?
Click to expand...
Click to collapse
Not to my knowledge. I guess we should *try* it just to see if there's a big difference... perhaps Neopeek can help us here muhahahahaha!
But I think the theory was the tradeoff would be small - a lot more work for very little reward. However, I would be interested to see if there is a difference, and if it is big or not. At the very least just to know if it's our build or just the ext2 partition that's making it feel snappier.
In addition, AFAIK swap partitions on SD cards should be avoided, unless they have a write-levelling scheme (I believe they only put these in SSD's... I don't think any SD card has this tech because it's typically unnecessary) - I've heard swap partitions can just destroy a normal SD card because of writing and re-writing to the same area of the card many, many times... I mean physically on the card, not just logically in the folder hierarchy.

Just installed it on my diamond Bluetooth does work but it doesnt pair. The screen eventually graduates to the center dividing it in opposite. I thought maybe because I was running the hot version. Repartitioned reinstalled the normal clock version runs for a time then the same. Its no better than XDA

[Q] What is the best technology (App2SD+, Data2SD, Data2Extv1,v2,v3 & v4 ?

Hello..
I need to know. what is the best technology in accordance with best performance (no lags), best memory (RAM) free, best sd card access speed, from
App2SD+
Data2SD
Data2Ext version 1
Data2Ext version 2
Data2Ext version 3
Data2Ext version 4
?

At the moment I think it's A2SD+, but in a few time, when developers modify and make a better DATA2EXT, I think it will be the best of all.

I agree with Neo. Data2ext isnt finished yet... need some more work For now i use A2SD+.

Agreed. I still use A2SD+.
Sent from my HTC Desire using XDA App

what i'm experience using data2ext. first boot takes too long. all performance seems many lags. when i'm restoring all of my sms & contact from mybackup app, it's very very slow..and it eats much RAM, until it hangs..i think data2ext version 1-4 is not suitable to be installed on our device for the moment. using app2sd+, app cannot 100% moved to sd card. installing hundreds of app can make internal memory full..

Im using DATA2SD and no problem
I recomend u to not use that chinese craps like data2ext

Moved to Q&A
Please do not post question threads in Development.
Post What Where:
General - general technical discussion items, news, anything else that does not fit into the other fora categories.
Q&A (Questions and Answers) - all questions, irrespective of type, get posted in here whether they be theme related, accessory related, technical, etc.
Accessories - any items to do with components and/or accessories relating to your device.
Rom Development - only meant for very advanced technical discussion directly related to ROM development activity and the delivery of actual ROMs and ROM components ONLY. Nothing else goes in here.
Themes & Apps - anything to do directly with the development of themes and/or applications. Nothing else goes in here.

dur09 said:
Im using DATA2SD and no problem
I recomend u to not use that chinese craps like data2ext
Click to expand...
Click to collapse
WOW. i have a question for you. can you make something better than that "crap"?

scottfu001 said:
WOW. i have a question for you. can you make something better than that "crap"?
Click to expand...
Click to collapse
Seriously man!! don't insult the developers who have placed some new concept in front of us!! You should be greatful that these developers and rom cookers are spending their precious time so that people can enjoy free good quality stuff

Scottfu001 said:
WOW. i have a question for you. can you make something better than that "crap"?
Click to expand...
Click to collapse
lordvoldemort said:
Seriously man!! don't insult the developers who have placed some new concept in front of us!! You should be greatful that these developers and rom cookers are spending their precious time so that people can enjoy free good quality stuff
Click to expand...
Click to collapse
I Think that was his Point, aimed at Dur09.....

Can anyone explain me differences between data2sd and data2ext? Both are symlinking whole /data partition to sd?

And could someone explain d2we?

I am also interested on the differences between data2ext, data2sd and data2we.
Noone knows?

i tried appsd+, data2w and data2ext...and i'm quietly sure that data2ext gets best performance scores between all, and it works great. i'm not a developer and honesly i don't understand technical details so much, i'm just a flasher but you can try data2ext.
by the way, i don't know how it was before

As far as I understand it, a2sd is Froyo's way of migrating apps to SD card, but then that feature is dependent on whether an app is coded to be movable. a2sd+ moves more apps to the SD card than a2sd, but still leaves plenty of "immovable" apps in the phone. Data2SD would be the one that moves just about everything to the SD card's EXT partition, while the rest of the data would be put in the FAT32 partition.

[Q] Low memory space on HTC Desire

I've just made a fresh install of android 2.3.3 but the phone keeps saying I have low memory (<20MB) on it. I've used app2sd to place ALL of the apps on the SD but no help still. I've tried some forums allready but I still have no idea how to fix this. Sometimes it can't even open my sms as it says the problem again is memory low.
If anyone can redirect me to some page or forum where this is resolved, or help me solve the problem.
Really sorry for taking your time if the solution is easier to find on google than I thought but I had no luck finding it.
Thanks in advance.
Other info: s-off-ed, android installed from http://htcdev.com/devcenter/downloads , for any other info just ask.
Also SD is 4gb.

With app2sd you will be able to move apps to SD (FAT32-partition) if the developer of the app included this feature. So I recommend to partiton your SD card with a FAT32 and an EXT4-partition with at least 1 GB (partition either with GParted or your recovery, if it supports it) and flash an A2SD+ or a DATA2SD-script via recovery.

check out supernova rom by droidzone. it gives unlimited internal memory.

+1 on supernova, works great!
Sent from my HTC Desire using XDA App

+1 for Sebs Runny mede 4.0.2.se but you need s-off and cm7/r2 with A2sdsx for unlimited (almost) space and a lovely fast ROM ta boot!
Sent with Desire.

angusc said:
+1 for Sebs Runny mede 4.0.2.se but you need s-off and cm7/r2 with A2sdsx for unlimited (almost) space and a lovely fast ROM ta boot!
Sent with Desire.
Click to expand...
Click to collapse
I agree Sebs Runny Mede 4.0.2.SE - super fast and stable but only if you use have CM7/R2 with A2SDSX. I have my ext 4 partition set to 1.5 GB and after install show 1 GB of internal memory for APPS. - WOW !

Thanks but I'm really keen on keeping this version of android on. I was actually wondering what could be causing this problem of low memory space as there is almost no apps on the device (I've moved everything to SD).
Could my problem be that I haven't formatted the device while I was reinstalling android or something????
So how can I solve the problem within this OS?
I can't believe that the internal disk is full when I have nothing on it. Could sms and e-mail really take that much space as I see only those two could be making the problem.
My phone says that there is 137mb used and 11free since I've installed the new OS. I thought the internal drive should be larger than that.
Really if there is no other way of solving this I might be willing to install the supernova but I'm really hoping there's some easier way.

grim2008 said:
Thanks but I'm really keen on keeping this version of android on.
Click to expand...
Click to collapse
Then you have to live with it.
I was actually wondering what could be causing this problem of low memory space
Click to expand...
Click to collapse
This problem of low memory space is, simply said, a problem of low memory space.
Really if there is no other way of solving this I might be willing to install the supernova but I'm really hoping there's some easier way.
Click to expand...
Click to collapse
Yep, there is an easier way: Seb's Runnymede AIO 4.0.3
Ok, seriously: Rooting and flashing is not that hard and worth the effort - but I would highly recommend Seb's Runnymede over Supernova, too, as it's way more smooth than Supernova, which was extremely laggy - at least on my Desire.
Greets, Magpie
P.S.: Your SD card should be at least Class 6 (and max. 16 GB).

Magpie42 said:
but I would highly recommend Seb's Runnymede over Supernova, too, as it's way more smooth than Supernova, which was extremely laggy - at least on my Desire.
Click to expand...
Click to collapse
OK, I was reading your posts in a few threads and now I see for sure you have no clue what are you talking about.
SwiftKeyed from my HTC Desire using XDA App.

erklat said:
OK, I was reading your posts in a few threads and now I see for sure you have no clue what are you talking about.
Click to expand...
Click to collapse
Ah, please enlighten me, how you know.
Greets, Magpie

Magpie42 said:
Ah, please enlighten me, how you know.
Greets, Magpie
Click to expand...
Click to collapse
If daily threads about smoothness and stability poping under Q&A couldn't enlighten you, I can hardly imagine there is anything I can do about that.
SwiftKeyed from my HTC Desire using XDA App.

erklat said:
If daily threads about smoothness and stability poping under Q&A couldn't enlighten you, I can hardly imagine there is anything I can do about that.
Click to expand...
Click to collapse
But you could at least try - or tell my Desire about these wonderful threads, which will make it run faster. And these threads, which will void my own experiences, the ones, I've seen with my non enlightened eyes ... at least they are mine.
Greets, Magpie - just own experiences count
P.S.: You may have heard already that there are a couple of different hardware combinations out there. And perhaps my Desire is on the slow side and probably my combination of phone and card may not be the fastest around, but, nevertheless, a phone/card, being on the laggy side, is an even better meter for the performance of a ROM than a phone/card which is fast anyway and will run at lightspeed with even a croppy ROM.

grim2008 said:
Thanks but I'm really keen on keeping this version of android on. I was actually wondering what could be causing this problem of low memory space as there is almost no apps on the device (I've moved everything to SD).
Could my problem be that I haven't formatted the device while I was reinstalling android or something????
So how can I solve the problem within this OS?
I can't believe that the internal disk is full when I have nothing on it. Could sms and e-mail really take that much space as I see only those two could be making the problem.
My phone says that there is 137mb used and 11free since I've installed the new OS. I thought the internal drive should be larger than that.
Really if there is no other way of solving this I might be willing to install the supernova but I'm really hoping there's some easier way.
Click to expand...
Click to collapse
Mate...as far as I can understand your issue, you do not want to change your Stock ROM but would want a space.....which I think would be a bit impossible somehow.....I mean, Come On...these guys are suggesting Great Solutions to your problem...the answer is in front of your eyes...if you're not into it then magic will most probably help you out..
So what would it be??

Unified Storage is Officially Coming

http://www.oppoforums.com/index.php?threads/20094/
I'm quite excited for this, even though Oppo is still lagging with Jelly Bean

Since it is uncertain when Color OS 2.0 stable will be finalized, I may jump on the beta wagon and try it out.
I am running out of storage space for my apps and I only have 1 game installed.

Yeah, it's a shame to have powerful hardware, but not really be able to use it much due to the storage limitation

anwedr said:
Since it is uncertain when Color OS 2.0 stable will be finalized, I may jump on the beta wagon and try it out.
I am running out of storage space for my apps and I only have 1 game installed.
Click to expand...
Click to collapse
But u could just move your apps and games to the 22gb phone storage partion?
I did this and have 2 pages worth of games in a folder including mc5, mc4, nfs most wanted, gangstar vegas, asphalt 8, nova 3 and dead trigger 1 & 2. I've even got offline gps maps and lots of arcade games in the games folder

jleslie97 said:
But u could just move your apps and games to the 22gb phone storage partion?
I did this and have 2 pages worth of games in a folder including mc5, mc4, nfs most wanted, gangstar vegas, asphalt 8, nova 3 and dead trigger 1 & 2. I've even got offline gps maps and lots of arcade games in the games folder
Click to expand...
Click to collapse
The color OS 2.0.2i beta only Supports Unified Storage, you will still have to use coolbird's partition tool to actually get it.
Read it here.

I was just talking about stable color os in general. I didn't realise you needed unified storage to get it. But i have been using stable jelly bean and you could move apps to phone storage as a default action. And it it's urge sane for the new kitkat update that they just brought out via manual update so i dont know why you'd want an unstable jelly bean color os Rom? The kitkat update brings alot of improvements overall as well. Although the launcher no longer comes with an app drawer. This didn't bother me as i use nova Anyway

jleslie97 said:
I was just talking about stable color os in general. I didn't realise you needed unified storage to get it. But i have been using stable jelly bean and you could move apps to phone storage as a default action. And it it's urge sane for the new kitkat update that they just brought out via manual update so i dont know why you'd want an unstable jelly bean color os Rom? The kitkat update brings alot of improvements overall as well. Although the launcher no longer comes with an app drawer. This didn't bother me as i use nova Anyway
Click to expand...
Click to collapse
Same for me too. I am happy with the way it is now, so long as updates and improvement keep coming. I am happy with the current launcher too.

The next COS beta will include the LVM method for unified storage
Not only the space is the issue, but that the play store is kinda buggy with this app partition way of things and it is frequently saying that you have insufficient storage available, even if you do have multiple times the space the app would need
Me too wanna use the unified on my find7, it would be a lot more easier to handle

jleslie97 said:
But u could just move your apps and games to the 22gb phone storage partion?
I did this and have 2 pages worth of games in a folder including mc5, mc4, nfs most wanted, gangstar vegas, asphalt 8, nova 3 and dead trigger 1 & 2. I've even got offline gps maps and lots of arcade games in the games folder
Click to expand...
Click to collapse
I did exactly the same thing. But everytime i restart my phone (due to BSOD mostly) all the shortcut on desktop would disappear. Not sure if im the only one.
Oppo Find 7 - CM141108
Regards, Zac.

A vigorous masturbation would make it come a lot quicker.
Seriously, you can't wait for OPPO to deliver - while everyone else is getting lollipop, we still have no OTA kitcat!

Can someone please explain this "Unified storage" thing to me? I dont really understand whats the case with the storage, but I can tell it is a problem to many since there is a partition fix flying around the development threads. I just got this phone second hand about a week ago and I am still discovering the way it works.
It came on ColorOS 2.0.0i based on 4.4.2, and I'm not even sure if its official.
I have however noticed some bugs with the UI and some random and fluctuating battery drains when it feels like it, although rare and my activities haven't changed much in terms of use.
Performancewise, well it gets the job done and seems to really rock the benchmarks I throw at it, and I do see this in real time when playing Beach Buggy Racing at maximum graphics, as well as Modern Combat 5, which weren't all that smooth on my S5.
Anyways, my main concern is a thorough explanation on the current storage issue, and why its getting a "unified storage" fix included in the future.

The Oppo Find 7 was released with a weird storage layout. You can only use 3 GB for apps, and the rest of the storage is used for user data (pictures, movies, and such). The original fix was to use a method that messed with the partitions to make the partitions work as intended. That method is dangerous.
Nowadays, the preferred way is LVM. This is the case with the latest beta. Not dangerous, and it can be done within the rom

farenteria said:
The Oppo Find 7 was released with a weird storage layout. You can only use 3 GB for apps, and the rest of the storage is used for user data (pictures, movies, and such). The original fix was to use a method that messed with the partitions to make the partitions work as intended. That method is dangerous.
Nowadays, the preferred way is LVM. This is the case with the latest beta. Not dangerous, and it can be done within the rom
Click to expand...
Click to collapse
Thank you. I never noticed that since I haven't surpassed 3GB worth of app data. Well, that depends if the application package is what counts towards the 3GB and the seperate data (e.g. what is found in the obb folder) is still considered as our own user space memory as per traditional partition layout.
Why make the partition like that in the first place when we have an SD card slot?
Hopefully I don't reach the limit as I don't want to have to try the mod.

I have no idea why Oppo did it in the first place, but the Find 7 isn't the first smartphone from the company to have that limit. I always thought that unified layout was the norm since Honeycomb, but I guess not

farenteria said:
I have no idea why Oppo did it in the first place, but the Find 7 isn't the first smartphone from the company to have that limit. I always thought that unified layout was the norm since Honeycomb, but I guess not
Click to expand...
Click to collapse
Ive come across my share of weird phone storage issues, like the Samsung Epic 4G which by default comes BML and many roms used the modified old school MTD partition map. Then there was the LG Optimus G, which when flashing a custom non stock based rom tends to hide all of your storage contents in the data/media folder. I could keep on, but the list would not end.
Now I can't remember which of my previous phones had this same issue, and it was annoying and confusing in the beginning...

Crossvxm said:
Thank you. I never noticed that since I haven't surpassed 3GB worth of app data. Well, that depends if the application package is what counts towards the 3GB and the seperate data (e.g. what is found in the obb folder) is still considered as our own user space memory as per traditional partition layout.
Why make the partition like that in the first place when we have an SD card slot?
Hopefully I don't reach the limit as I don't want to have to try the mod.
Click to expand...
Click to collapse
It's basically that Oppo was one of the last companies to move away from the "legacy" layout.
Google started using emulated storage with Honeycomb, but it wasn't until maybe a year after ICS that most phones moved to the "new" method. Xperia T (late 2012) was one of the last ones I remember like that.
I think that it's partly due to the fact that Windows XP is still dominant in China - Its MTP support is poor, and Chinese users apparently prefer UMS. I remember at one point (around the time the N1 was released) that someone from Oppo was asked why they used the "old" partition method and their response was "user preference". While that might make no sense to a Western user, it makes sense when your home market is China. Chinese tastes are very different from Western tastes. Of course with the Find7, Oppo kind of screwed up by using ext4 for the internal SD partition, rendering it useless for UMS + WinXP.

Entropy512 said:
It's basically that Oppo was one of the last companies to move away from the "legacy" layout.
Google started using emulated storage with Honeycomb, but it wasn't until maybe a year after ICS that most phones moved to the "new" method. Xperia T (late 2012) was one of the last ones I remember like that.
I think that it's partly due to the fact that Windows XP is still dominant in China - Its MTP support is poor, and Chinese users apparently prefer UMS. I remember at one point (around the time the N1 was released) that someone from Oppo was asked why they used the "old" partition method and their response was "user preference". While that might make no sense to a Western user, it makes sense when your home market is China. Chinese tastes are very different from Western tastes. Of course with the Find7, Oppo kind of screwed up by using ext4 for the internal SD partition, rendering it useless for UMS + WinXP.
Click to expand...
Click to collapse
It makes sense. In terms of the Xiaomi Mi3W and this one including a theme store which themes beyond just the app icons, you can tell it is something designated for a non US area. Here in the US, it's mainly about high end and so on. Most of the Chinese do not complain if they're device is falling behind the rest when their phone has a Snapdragon 800 meanwhile every other phone getting the 801. As far as storage, I don't see why they would keep the outdated way as a preference when the phone includes a Micro SD card option and so on, and you get more versatility when the storage is combined as all current phones have.

Cancelled after reading other posts !
---------- Post added at 03:06 AM ---------- Previous post was at 02:42 AM ----------
Lord Childe said:
A vigorous masturbation would make it come a lot quicker.
Seriously, you can't wait for OPPO to deliver - while everyone else is getting lollipop, we still have no OTA kitcat!
Click to expand...
Click to collapse
OTA Kitkat is to come next monday 26.01.15 !
Google to : Find 7/7a ColorOS V2.0.5i Beta | OPPO Forums
About Lollipop, after so many complains, it seems to me urgent to wait !
Except for geeks who like to struggle with beta, it's better to wait Lollipop better version.
The only 5 feature I really miss is the recovered ability for apps to write to SD card.