Database Info

[ROM][32A RADIO 6.35]Eclair w/ Nexus1's 3D gallery CAM & most things are working well

[ROM][32A RADIO 6.35]Eclair w/ Nexus1's 3D gallery CAM & most things are working well
this ROM is for Sapphire 32A SPL 1.76.2007 and latest Radio 6.35.07.29.
pure AOSP build, google bits and gallery are added. (make sure you think you have the rights for using the apps from google, i just make some copy for you)
thx: Cursordroid, Enomother, Cyanogen, RA, jnwhiteh, ChainsDD, sober (who have full of courage for testing my first kernel ) , and more...
what's new: less crash, more stable. new gallery app which use hardware accel. a new step to full working with our new radio.
the update.zip, just push it into ur sdcard then apply it from recovery: http://www.4shared.com/file/202007372/5352e8b4/my2x.html
mirrors:
http://hotfile.com/dl/24995574/2b6c9d7/sanpei_eclair32a.zip.html , by asero, thanks
http://www.megaupload.com/?d=5TH7FNC0 , by akai21, thanks
http://hoegsberg.net/fileshare/Sanpei Eclair 2.1/ , by Eukanaba, thanks
if you are a 32A user with old radio, and you want a upgrade or try this ROM, follow Cursordroid's instruction to Update your 32A Magic to 6.35.07.29 Radio and 1.76.2007 SPL
working (update: all confirmed by me or other users):
camera
gps
wifi
mobile data
sensor
lights
gps
bluetooth
openGL
Gallery3D
googlebits
working but leaving some questions open:
playback (will print error message in log, not tested with many format)
not working properly:
camcorder (only preview working)
I would not say "it is very fast", but I feel it fast enough. and if you do not care about the multi-media things, i think this build seems not bad.
(for the multi-media things, they are mostly caused by media libs in AOSP, which google have not done yet. (but i cannot understand why nexus-one can have a stable version !!!) it is not all the HTC/Qualcomm's fault, Google didn't do their job very well too)
if there are something I missed, or I made some mistake, don't be sulkiness plz. i will fix them with you. let us make it better and make more 32A user switching to new Radio, with more users, we can do better and more quickly.

file/things includes:
AOSP master, I keep it at the API version 5, because things with API 7 for other devices (except nexus1) are not stable, i don't want to pretend that we have a nexus1, and make things unstable.
su and superusers from ChainsDD.
kernel which i modified from msm-kernel-2.6.29.
libhtc_ril.so, omx libs are from a leaked official 2.x ROM. camera libs, libgps.so from another one. (thanks the man who provided them)
libhtc_acoustic.so and some miscs files from official 1.5 ROM. akmd too, but akmd from 1.6 ROM have newer version and i think it will works too.
google bits are come from different sources too:
Gallery3D/google framework parts from nexusone dump, i think Enomther deodexed them, thank you and I LOVE YOU.
Other google's things are versions used everywhere, and here are my thanks to the one dumped them --> m(_ _)m.
cyanogen's patch which is directed towards infinite sync. it may be a temporary workaround, when google do things right, i will remove it.
.......
more: lock screen and wallpaper is the eclair's initial one as AOSP source released with them. if you want other lock screen, customize it yourself, and tell me how ^^, I'm really not a good cooker .

known issues and workaround:
1. camcorder can not record, but it didn't crash anything as previous one (with my kernel, from jnwhiteh) would crash some.
2. video playback has many errors the video can be played though. just reported by logcat, and no more thing will happen in my tests.
3. if you stay in the Gallery3D UI, and the phone sleeps later, when it wake up, the Gallery3D lost hardware acceleration. you can quit and enter this app again, it will be fine.
4. first boot with google bits may not go without a hitch. you can remove all google apps in the zip (you must resign it) and push them later.if you boot with googlebits:
you will see a dialog let you choose the default behavior, select SetupWizard here. if you select another, you can not use internet during the first boot, it will say "no connection", though we are connected.
the SetupWizard will start twice, the second one is for asking you to sign in a google account, you can just press menu to quit.
and there are many lags in first boot, maybe black screen (can not light, you can "adb reboot" it) or some crash (i have met once for each and I flash it serveral times) if you operate too fast.
after second boot, it will works fine. it seems if we give the phone more time to do many initialize jobs, it will work happily even in first run.
5. with superuser, if you select deny, the app which needed the permissions may be force closed. it is a bug in su sources i used which is not belong to me and i have no time to look and fix it yet.
update:
6. when wake up the phone, screen turned on, but backlight of screen not. if you can see image, just go to setting and set brightness, then the light will open. need more reports (like situation/logcat/dmesg, etc.) to locate the problem. i encountered this problem once.
7. "died in sleep", this problem has been encountered by others, personally, i met it once during first run, after a reboot I never met it again. but I don't think this problem just appears during first run. instead, i think the situation of first run is more closed to the condition triggering it.
I think there must be more problems, let us find them together, and fix them by our hands.
update: after some search I found that some softwares (like nettraffic) will cause more "died in sleep" in some ROM/kernel/Radio combination. and many kinds of "died in sleep" can be avoid with some tweaks, but i don't know if they are same problems as ours, and i can not get what this tweaks are (or why, how..) from anywhere yet.
i am waiting for more details to fix 6 & 7. I will be grateful if someone can provide some info about similar problems, since I had seen these problems in some other ROM/kernel/Radio combination.
and guys who encountered these problems, could you provide more details plz? something like: occurred during first run/other, with situation XX (mobile/wifi/software X running, etc) which you think it caused the problem occurred more often. if you can reproduce it, we will get very closed to fixing them.

great job!

Another ROM using the latest SPL/Radio... great!
Downloading now.. will try flashing later...
Nice work sanpei!

Great job. I will try it immediatly.

Excellent, nice to see some other developers working on this radio/SPL version as well!
I will definitely be trying this out today!

Awesome will try when I get home from work.
Would it be possible to implement the Nexus apps-menu in a later build?

bug report:
The screen remains black (can't see anything) after sleeping even if I press any of the buttons. I just removed the battery then reboot.
Aside from that, it's quite fast and responsive. The transitions are nice too. Keep it up dude!

asero said:
bug report:
The screen remains black (can't see anything) after sleeping even if I press any of the buttons. I just removed the battery then reboot.
Aside from that, it's quite fast and responsive. The transitions are nice too. Keep it up dude!
Click to expand...
Click to collapse
I will look into this, but I cannot locate this problem quickly, since I just met it once during a first boot, and it never appears again.
is it like the situation "die in sleep" in some build which are based on CyanogenMod? (when i was using old radio)
can you reproduce the problem and description the operations? thx.
Eskibo said:
Awesome will try when I get home from work.
Would it be possible to implement the Nexus apps-menu in a later build?
Click to expand...
Click to collapse
maybe or maybe not is there anybody who have the right skills could try it for us? (i have some other things to do) i will join later.

Newb questions
Hi Guys,
Sorry for the lame newb questions. I just want to verify this prior to trying this ROM.
I'm currently using CursorSense 1.0.1 - which is my every day ROM (great functionality, fast, does everything I need)
I'm really interested in trying out Android 2.1 - and seeing as this uses the same SPL / Radio - it means I should be able to just wipe and flash this one. HOwever seeing as I just want to take a peek and play around with it, I don't want to screw up everything on my phone toooo badly lol.
If I do a nand backup - wipe and flash this new ROM, when I'm done, can I do a wipe, then reflash the nandroid backup and everything will go back to the way I have it setup now?
Also will anything get screwed up on my SD card leaving it as it is flopping from one ROM to the other and then back (it's non partitioned, and loaded with misc folders created from my apps)
Thanks!
Gritten

asero said:
bug report:
The screen remains black (can't see anything) after sleeping even if I press any of the buttons. I just removed the battery then reboot.
Aside from that, it's quite fast and responsive. The transitions are nice too. Keep it up dude!
Click to expand...
Click to collapse
I encountered this issue too. I also encountered this issue once with aosp-2.0.1-jnwhiteh-r6.

Gritten said:
Hi Guys,
If I do a nand backup - wipe and flash this new ROM, when I'm done, can I do a wipe, then reflash the nandroid backup and everything will go back to the way I have it setup now?
Also will anything get screwed up on my SD card leaving it as it is flopping from one ROM to the other and then back (it's non partitioned, and loaded with misc folders created from my apps)
Thanks!
Gritten
Click to expand...
Click to collapse
Yes.. backup, wipe, flash, try, wipe, restore.. I even think that last wipe isn't even necessary, but it doesn't harm either. A Nandroid restore restores your phone exactly as you left it (incl. your call log, SMS, apps, etc.)
It could be that some new folders/files are created on your SD card (if required by Eclair apps), but since they are not used by your previous rom it won't be a problem (unless you don't want to keep those unused folders and files on your SD card).
If you are not sure, or don't want to keep the extra folders/files, you can always make a backup of your SD card on a USB or PC prior to trying the rom.
Have fun! ;-)

Gritten said:
Hi Guys,
Sorry for the lame newb questions. I just want to verify this prior to trying this ROM.
I'm currently using CursorSense 1.0.1 - which is my every day ROM (great functionality, fast, does everything I need)
I'm really interested in trying out Android 2.1 - and seeing as this uses the same SPL / Radio - it means I should be able to just wipe and flash this one. HOwever seeing as I just want to take a peek and play around with it, I don't want to screw up everything on my phone toooo badly lol.
If I do a nand backup - wipe and flash this new ROM, when I'm done, can I do a wipe, then reflash the nandroid backup and everything will go back to the way I have it setup now?
Also will anything get screwed up on my SD card leaving it as it is flopping from one ROM to the other and then back (it's non partitioned, and loaded with misc folders created from my apps)
Thanks!
Gritten
Click to expand...
Click to collapse
Yes. You can restore from nandroid backup and everything will go back. I often switch between CursorSense 0.4 and sanpei's rom several times a day.

so can anyone answer if this is a good everyday rom? or equivelant to cursor sense?

shael said:
so can anyone answer if this is a good everyday rom? or equivelant to cursor sense?
Click to expand...
Click to collapse
The ROM is well done. It's responsive (no lag from my playing) even the 3d gallery ran very well.
I didn't use it too long for everyday items as I'm a Sense fan, however I find that standard plain Android is pretty empty when I don't have my sense stuff on top lol.
Definately play around with it if you're interested.

sober said:
I encountered this issue too. I also encountered this issue once with aosp-2.0.1-jnwhiteh-r6.
Click to expand...
Click to collapse
Me too!
Awesome ROM.
Keep UP dude!

Been testing it for a few hours. So far not a single FC and i can confirm that BT works just fine, also OBEX with Bluetooth File Transfer by medieval software.
SMS and emails send and get received just fine.
Tested the GPS in both google maps and the GPS status app to check efficiency, and so far everything works just fine.
The gallery is really sexy, now we just need to get the Nexus1 apps-menu implemented .
Actually there are three other things i'd like implemented also:
Animated desktop
Wireless tether
Google Nav
What do people think about that?

Eskibo said:
Been testing it for a few hours. So far not a single FC and i can confirm that BT works just fine, also OBEX with Bluetooth File Transfer by medieval software.
SMS and emails send and get received just fine.
The gallery is really sexy, now we just need to get the Nexus1 apps-menu implemented .
Actually there are three other things i'd like implemented also:
Animated desktop
Wireless tether
Google Nav
What do people think about that?
Click to expand...
Click to collapse
Will be even better with u suggestion and Sense!

fabioccoelho said:
Will be even better with u suggestion and Sense!
Click to expand...
Click to collapse
I wish I had some idea of how to do those things, then I would surely try help doing it.

[ROM] Modded Super D with dwang's kernel

As I`ve posted before some code in most new kernels is causing some issues while using my car's handsfree set(vw) I get random disconnects.
So as I like Super D and I like latest dwang's rom. I mixed both of them and took the best of both roms. What you get with this rom is latest Super D with the best kernel that's working for me.
i don't take any credit from it, I'm sharing a good setup working for me. I just took all the work done by people involved in Super D and Dwang's rom. Apart from that I also included advanced launcher themed by eesel with cyanogen's tray shape.(thanks rogro82, cyanogen and eesel)
Link:
http://www.megaupload.com/?d=V5H2P9IE

Trying will report back
thanks for sharing friend!
Edit:
1. Speed is good
2. Sometimes launcher lags in sweeping
3. No MT anywhere, well thats the Kernel thing
4. sign-in page force-closed on me many times but got over with that
5. Killing all the apps gives 60 MB free, wwhile on SD default kernel we get around 45 MB, this is great!
6. application response is very very quick
7. wall-paper gallery is older
Thats all for now....hope it helps those wanting to try this ...
Cheers,

I am not having those issues. Have you wiped everything before flashing? I didn't have any force close in the whole friday.
I have to research how to solve multi touch issue, because dwangs rom supports it

Wow, superb work. I may test it asap.
Hows battery life compared to stock SuperD? That was the thing put me away from Dwangs (and the random reboots).
Thankyou!

sounds interesting.

xabierd said:
I am not having those issues. Have you wiped everything before flashing? I didn't have any force close in the whole friday.
I have to research how to solve multi touch issue, because dwangs rom supports it
Click to expand...
Click to collapse
-no idea then, coz mine asked for re-inputting log-in information again and again. although everythhing was setup (meaning, synching was running while it was still bugging for signing in to google after I did it once)
Coming to your question, ya I always do full wipe, no matter what.
Your Mod definitely runs fast, congrates, and the force close is only stopped once you ignore signing in request and press Home button - done!
MT is an issue fr me, not that I use it while browsing web or Gallery very often but I like to have it for the sense of completeness
Good Job, I am now back to SupD tho.
P.S. Battery was not checked since I only stayed on this rom for less than an hour, not enough time right?
cheers

Battery life *seems* good so far
Multitouch is working indeed BUT not in the browser nor the photo gallery, I still have to look for more info. If you want to try it run MT visualizer. I 'm sure it's something about multitouch being handled in different way by donut or eclair.

I just flashed it without a wipe.
It works fine for me so far, but it should be mentioned that it is the white version
But i like suprising graphical changes

arefin said:
thanks for sharing friend!
Edit:
1. Speed is good
2. Sometimes launcher lags in sweeping
3. No MT anywhere, well thats the Kernel thing
4. sign-in page force-closed on me many times but got over with that
5. Killing all the apps gives 60 MB free, wwhile on SD default kernel we get around 45 MB, this is great!
6. application response is very very quick
7. wall-paper gallery is older
Thats all for now....hope it helps those wanting to try this ...
Cheers,
Click to expand...
Click to collapse
60 MB free? "
It use ramhack, compcache and swap?
BTW.. seriously.. The kernel have ramhack, right?
Now I'm using the rom SuperCSDI V1, and with the SupSetup I can turn on or off APP2SD.
I think it's a great thing, because installing apps on NAND they run a lot faaaaaaaaaaster! So I install default apps in NAND, and other apps in ext partition.
If I found a way to do it in this rom, I'll try it
PS: If you don't use compcache or swap and it have 60mb free on killing.. ramhack can be removed to use 3D application

xabierd said:
As I`ve posted before some code in most new kernels kernel is causing some issues while using my car's handsfree set(vw) I get random disconnects.
Click to expand...
Click to collapse
OMG i have the same exact issue with the random disconnecting. its been prevalent in every rom since cyan's 4.2.6 (and dwangs, super D, etc). I've tried pushing the older working "bluetooth.apk" from 4.2.6 to the newer builds with no success at all. Did you recompile the ROM to make it work? The perfect ROM to me would be Super D 1.9.2 with no ram hack and working bluetooth.
good work though, im willing to sacrifice 3D games for working bluetooth though so i may give this a run... *subscribed!*

sounds good flashing

nice Rom, but it only has 3 screens, and i don't like the launcher. Despite those things its great, i did a few tests
benchmark
lowest - 625
highest - 1084
ram
after killing all of the tasks i had 50mb

zachattack052 said:
nice Rom, but it only has 3 screens,i dont like the launcher
Click to expand...
Click to collapse
You can have up to 10 screens: menu -> more
And there are enough themes for the advanced launcher

ID# said:
You can have up to 10 screens: menu -> more
And there are enough themes for the advanced launcher
Click to expand...
Click to collapse
O wish i knew that before. than that solves the things i didnt like about it.

After killing all apps I still have around 40-43 mb.

quierotacobell said:
After killing all apps I still have around 40-43 mb.
Click to expand...
Click to collapse
thats normal for a donut rom

zachattack052 said:
thats normal for a donut rom
Click to expand...
Click to collapse
Yeah but that one guy got it over 50 just curious thats all.

dzasta said:
OMG i have the same exact issue with the random disconnecting. its been prevalent in every rom since cyan's 4.2.6 (and dwangs, super D, etc). I've tried pushing the older working "bluetooth.apk" from 4.2.6 to the newer builds with no success at all. Did you recompile the ROM to make it work? The perfect ROM to me would be Super D 1.9.2 with no ram hack and working bluetooth.
good work though, im willing to sacrifice 3D games for working bluetooth though so i may give this a run... *subscribed!*
Click to expand...
Click to collapse
What hands free set do you use?
I've read that you can solve it by editing /etc/bluez/audio.conf as follow
enable=
Disable=Headset,Gateway,Source,Control,Sink
uncoment #Master=true and replace it by Master=False (mind the caps)
It's working for BMW sets, give it a try may be you can keep 3d.

xabierd said:
What hands free set do you use?
I've read that you can solve it by editing /etc/bluez/audio.conf as follow
enable=
Disable=Headset,Gateway,Source,Control,Sink
uncoment #Master=true and replace it by Master=False (mind the caps)
It's working for BMW sets, give it a try may be you can keep 3d.
Click to expand...
Click to collapse
I drive an audi A3, and the OP drives a VW which most likely uses the same BT system. I just finished pulling the audio.conf from the phone and will edit it like you said. *fingers crossed* will update tomorrow...
UPDATE: The bluetooth fix mentioned by xabierd seems to have fixed my random disconnecting issue. didn't drop the connection once during my 30min commute to work. i normally experience at least 2-3 random disconnects every time i drive to/from work. yay!~!!

I'm glad I helped you, I am the OP too

[GUIDE] ANDROIND 2.2 FROYO For HD2 (no joke)

I haven't seen an easy step by step guide for getting ANDROID 2.2 aka (Froyo) on the HTC HD2 .
Just download this file here: http://x.vu/HD2ANDROID
extract and run.
thats it!
ENJOY

The link is not working

Hi,
look here:
Development Thread > http://forum.xda-developers.com/showthread.php?t=719646
Android Builds > http://gamesquare.co.uk/
with friendly greet
starbase64

starbase64 said:
Hi,
look here:
Development Thread > http://forum.xda-developers.com/showthread.php?t=719646
Android Builds > http://gamesquare.co.uk/
with friendly greet
starbase64
Click to expand...
Click to collapse
ok,it works fine but i have some problems!I can make calls but i cant hear my caller neither he.I can also send sms.I have the last energy above with 2.12.50.02_2 radio.Now its ok!Also how can i see my contacts or to sync with what application?I am hearing very very slowly the other person?Do you know why?

noolis said:
ok,it works fine but i have some problems!I can make calls but i cant hear my caller neither he.I can also send sms.I have the last energy above with 2.12.50.02_2 radio.Now its ok!Also how can i see my contacts or to sync with what application?I am hearing very very slowly the other person?Do you know why?
Click to expand...
Click to collapse
Hi Noolis. Let me tell you that just like you, most people on the HD2 (including me) are waiting patiently for the Android OS to work as perfect as any other native Android Device. The guys on the main thread are working very hard for this to happen.
Just bookmark the following thread and visit it everyday. read the information on the 3rd post, and try their work in progress at your own risk. enjoy
this is the thread: http://forum.xda-developers.com/showthread.php?t=719646
Bookmark it, it'll make it easier for ya!!

i keep gettin a green screen then it freezs, i downloaded the zip to the sd card then i extract all the files then run the haret and it goes all the way to the drawling of the android and about a min. after it gets a green screen , what am i doing wrong please

i got that green screen as well but after a new restart it worked perfectly...
And before that i did have the error message "waiting for SD card" for a long time.
Even I dont know how I get Android running on my HD2...
Maybe just restart and retry, who knows!
Good luck

Android probably won't be working right for a number of months. Its ok though. The apps are nice but WinMo is still ok for apps (no calc on droid is as good as the panoramic one, Igo Primo > Igo Motonav, etc). By the time droid apps are leaps and bounds better, android should hopefully be working great on the hd2.
I say, just peek at it once in a while but don't really worry about it for another couple months.

Can somebody make a video for the new rom out?

How to make the Anroid OS working on the HD2 - Step-by-step instructions, FAQ, Tweaks
UPDATED! Read the informations & FAQs below...
For those who have got difficulty in making the ported Android builds working on their HD2, here is a step-by-step description!
Accessories:
- First thing you need to have is: The newest Jmz Android dual-boot program, which can be found HERE! The program must have installed in the Device memory!
- Another thing you have to have is a freshly-formatted SD Card (I recommend 2GB or bigger, but in theory the Android will work with a 1GB or less (the least is 512 MB) card...)
- A ported Android ROM (e.g. 2.1, Froyo, Desire ROM, usw.) You can find some working builds HERE! (Desire ROM, Froyos, Ubuntu builds)
Instructions:
- Firstly, install the latest Jmz dual-boot app (v3) into the Device memory!
- Download the Android build and copy it into the ROOT of your freshly-formatted memory card! Normally you just have to copy the files into your card, but in some cases you have to copy the whole folder though... (for more infos check out the build's README file, if it has got one)
- If it's needed, RENAME the "zharet" file to "haret" and the only txt file (Unluckily I don't know what its name is at the moment, I remeber to "README.txt" or sgh, but now I don't have any builds in which the name of these files are not these names) to "startup.txt"!
- Instert the card to your HD2!
- Restart your device!
- When the boot-screen appeares and starts, choose the "Boot Android" option!
- Wait for the Android build finally starts up (it takes 2-3 minutes or more, it depends on the ROM)
- Use and enjoy it!
If you still have problmes with the installing, send a PM or reply a comment!
I hope I could help with this.
[Please excuse me if I made any grammatical mistakes...]
IMPORTANT! You're really ought to make a full-system-backup before trying ANY of the ported builds out! (I recommend the SPB Backup, but of course, another backup progs are such suitable... either of them will do it!)
For example one of these builds blew my Sense 2.5 sky-high, and unluckily I didn't do a system-backup before I had tried the ported Froyo build out. As a result, I had to modify and customize my Sense again...
And according to my friend, due to an Android build, his 3G-data connection setup has also been laid down... so be careful, for all that that the most of these releases are "harmless"!
UPDATE (updated at 07/19/10):
For example I've just tired this build: "New Froyo build by dan1j3l V1" (description and DL link can be found here...), and it works very well on my HD2! It is fast, smooth enough, all of the wireless connections are working (just like BT, Wi-FI), and so on... worth a try!
IMPORTANT UPDATES AND FAQs
Q: Some people asked me how could the sound working without starting CLRCAD manually...
A: The Jmz dual-boot application automatically starts it, you needn't do it manually!
Q: Why is it not necessary to run "(z)haret"?
A: The answer is the same: the Jmz automatically does it...
If you have still have issues with the Android builds (e.g. with the backlight), try out these tweaks:
- To prevent your device from freezing when it tries to sleep, set the screen's timeout to 30 minutes in the ANDROID settings!
- Turn off "Automatically adjusted backlight" in the WinMo settings (or in the Sense 2.5 settings, makes no difference), and set both backlight option to 100%!
- UNCHECK the "Dim backlight if device is not used for XY minutes" option, and "Turn off device if it's not used for XY minutes" as well! (At the "On Battery Power" or "On External Power" section, it depends on what power-option you'd like to use your phone in...)
If your build doesn't show, or shows wrong the battery-meter (e.g. your battery is fully charged, but the build shows a "?" mark insted of the precentage or ask you to recharge it, etc.) (... and if it's not able to handle it), download this file and copy it into the root of your SDCard, and replace the original with it!
DOWNLOAD (FTP Mirror)
Unconfirmed tweaks:
- If you are able to run the builds in no way, try to format your SD Card in FAT32 filesys. It answered the problem for some people...
- In theories, HSPL is needed to run the ported Androids, but this assertion is unconfirmed at the moment!

not being funny but shouldn't you have posted this in general as android isn't exactly a theme is it ?

Not it's not a theme but the other half of the thread section is Apps. I take Android as as App when it's not a flashed OS.

just installed android using this guide, very helpful so thanks.
im using 2.2 Froyo build by dan1j3l and it seems to work very well. data connection seems slower then on WM, the battery meter doesnt work (and i cant charge the phone or connect it to the PC) when the phone goes into standby, it keeps the backlight and buttons on. also have the issues that many users are experiencing with calls. also when i reboot into windows mobile, the time and date reset!
just to help people out that maybe dont have much experience with this (such as my self) maybe you could add things such as radio ROM requirements, and perhaps a list of things that arnt working accross all ROMs (i think the call issue would be an example of this). you can find it through searching, but its nice to have it all in one place
if it helps i think you need radio 2.08 or above but not 2.12 (2.11 is the latest radio that works), as well as HSPL installed. the 'green screen' seems to be a big issue, but i just removed the battery and re-inserted it and it worked fine

matthewharmon102 said:
just installed android using this guide, very helpful so thanks.
im using 2.2 Froyo build by dan1j3l and it seems to work very well. data connection seems slower then on WM, the battery meter doesnt work (and i cant charge the phone or connect it to the PC) when the phone goes into standby, it keeps the backlight and buttons on. also have the issues that many users are experiencing with calls. also when i reboot into windows mobile, the time and date reset!
just to help people out that maybe dont have much experience with this (such as my self) maybe you could add things such as radio ROM requirements, and perhaps a list of things that arnt working accross all ROMs (i think the call issue would be an example of this). you can find it through searching, but its nice to have it all in one place
if it helps i think you need radio 2.08 or above but not 2.12 (2.11 is the latest radio that works), as well as HSPL installed. the 'green screen' seems to be a big issue, but i just removed the battery and re-inserted it and it worked fine
Click to expand...
Click to collapse
if you are using any of the android builds ie dans froyo or desire there are a couple of different zimages that you can replace in your android file. these will sort out the dimming isssue and have camera working, calls are perfect on my 2 different versions although 1 has accelerometer & no camera and the other is the opposite way round, battery is charging and indicators are working but i havent tried all the zimages to say what else they have up their sleeve so to say.
In regards to radio it needs to be a min of 2.08.50.* mine is 2.12 and calls are clear as a bell although browser can be a bit of hit & miss at times, it is getting better as different builds come out so well just have to be patient til a rom is eventually released.

i keep getting a green screen after the drawling of the android , it will drawl the android a couple times before the green screen pops up and freezes and i cant find anyone to help me out , ive read the directions but the last pass 24 hrs nothing but a green screen

Excellent guide Kromosome !
But I have the same issue as matthewharmon102.
In plus my HD2 it not responding after going to sleep ...
I'm confident that in the next release some of this issues will be solved.
Thank you guys

android not working
i have installed Jmz dual-boot app (v3) into the Device memory.....after restart boot menu appears ,i selected android it starts installing haret...after some time my screen went dull wit some lines and freezed.... Android is not working...am getting mad..plz help me out... :-(

android not working in my HD2
i have installed Jmz dual-boot app (v3) into the Device memory.....after restart boot menu appears ,i selected android it starts installing haret...after some time my screen went dull wit some lines and freezed.... Android is not working...am getting mad..plz help me out...

Hey everybody!
Some people asked me about the instructions, so I've modified my guide, and I wrote some important informations into it, and I integrated a FAQ section (that will probably increase), which is worth to be checked out!
I've also written down what you should do if your device freezes when you try to awake it, or if your screen goes dull after the Jmz starts installing the "haret", and tries to set the Android OS up!
If you have issues (especially backlight-issues), don't forget to check it out!

Hail Everybody!
As we know the Android developers are working hard to make it run smooth on our HD2.
There still bugs here and there but for sure we will get this great thing smooth like our WM OS soon!
Keep up the great work!

What's the best Android ROM for Polaris?

I am sorry if a thread like this exists but I didn't managed to find it.
I tried different Roms but I can't remember from all which is the fastest.
I am mainly using my Polaris for:
- phone calls
- wifi browsing: Opera Mini/Skyfire
I want the fastest Android Rom that will suit my needs. From your experience what ROM would you recommend me ?
Thanks.

Try to use froyo 2.2 RLS 12, right now i use it on my phone, it is fast naught to do all the usual things without wait. I overclocked my CPU to work at 540MHz (this says Rogue Tools) but it is working at 520MHz really. The market it is working fine, bluetooth also, wifi can be solved to obtain ip, everything is ok. If you wanna more details, PM and i will try to guide you in romanian

BYTeXperience said:
Try to use froyo 2.2 RLS 12, right now i use it on my phone, it is fast naught to do all the usual things without wait. I overclocked my CPU to work at 540MHz (this says Rogue Tools) but it is working at 520MHz really. The market it is working fine, bluetooth also, wifi can be solved to obtain ip, everything is ok. If you wanna more details, PM and i will try to guide you in romanian
Click to expand...
Click to collapse
how can I flash froyo 2.2 RLS 12 to my Polaris?wifi is ok?

1. READ POST1 HERE - FOR THE INSTALL PROCESS INSTRUCTIONS and download the install-seq.sh .
2. READ POST1 HERE - DOWNLOAD THE Latest FroYo NBH or ZImage (POLAIMG.NBH) for your panel type, and the RLS12 All Languages Themed (androidinstall.tar).
3. READ POST1 HERE - FOR THE NBH Editor v3.5.2 YOU CAN DOWNLOAD AND USE THIS PROGRAM TO CHANGE THE PANEL TYPE FROM 1 TO 3 OR FROM 3 TO 1.
After you read all the 3 posts from the 3 thread and you download all the files you need you can proceed with the install using the steps described in the point 1.
For solve the WiFi obtain IP adress, after you install successfully the Android on your Polaris, restart it and press the volume button up when booting Android, you will see a menu with some options, select FIX PERMISSIONS menu and wait... after the fix WiFi will work just fine and it will obtain the IP from the network.
Hope this post will help you.

Indeed, I am using since yesterday RLS12. It is pretty ok, some freezes here and there but nothing really important. Sometimes in Market the phone restarts. I thought about overclocking the CPU but I was affraid not to broke it. Is it safe? Is there a performance improvement ? What about battery drain ?

In my case i don't have any problems with freezes or restarting in the Market, but when you change the camera settings application from photo to video then the program stops. About overclocking the CPU, i use it in this way (540MHz) from some time, all is ok, the phone is fast and the battery is not drain, in my case work from 3 days ago and i have use it my phone to calls, WiFi (browsing), Bluetooth (send/receive files).

this last several days i've spent time to try a lot of android build for my device polaris100. here is my opinion about the best adroid build i've tried :
1.Incubus26jc's Super Froyo (RLS13)
the best build for show off to your friend in reality my device's 128 mb ram can't run it as smooth as it should be. too many frezes it work but with limitation. you need to tweak it a bit to make it bearable : 1 launcher page, keep launcer on memory, kill all windows animation. try to move the installed program to your sd might increase the cache files. uninstall those you never use. minimal widget. you might want to overclock your procc at the risk of your beloved polaris.
2. Kallt_kaffe VaniljEclair RLS11 (CM5.0.8)
It has the bling bling as the froyo build but it works generally alot of better than the froyo one. it work fast out of the box. and if you do the tweak i mentioned above it work alot of more faster. but not as fast as it should be if compared to those official device that came out with eclair.
3. [ANDROID] Myn’s Warm Donut - [RLS 5 - 04/24/2010]
this is the oldest adroid of the two above. but it has the least hardware requirement, in other word it really work as it should be (compared to the device that officially came with it). it just some glitches here and there but it is bear able. I'm having alot of fun with this build.
there is alot of other build that i tried but IMHO those 3 above are the one worth to mention.
hope this help.
CHEERS!

Tjahjo07 said:
this last several days i've spent time to try a lot of android build for my device polaris100. here is my opinion about the best adroid build i've tried :
1.Incubus26jc's Super Froyo (RLS13)
the best build for show off to your friend in reality my device's 128 mb ram can't run it as smooth as it should be. too many frezes it work but with limitation. you need to tweak it a bit to make it bearable : 1 launcher page, keep launcer on memory, kill all windows animation. try to move the installed program to your sd might increase the cache files. uninstall those you never use. minimal widget. you might want to overclock your procc at the risk of your beloved polaris.
2. Kallt_kaffe VaniljEclair RLS11 (CM5.0.8)
It has the bling bling as the froyo build but it works generally alot of better than the froyo one. it work fast out of the box. and if you do the tweak i mentioned above it work alot of more faster. but not as fast as it should be if compared to those official device that came out with eclair.
3. [ANDROID] Myn’s Warm Donut - [RLS 5 - 04/24/2010]
this is the oldest adroid of the two above. but it has the least hardware requirement, in other word it really work as it should be (compared to the device that officially came with it). it just some glitches here and there but it is bear able. I'm having alot of fun with this build.
there is alot of other build that i tried but IMHO those 3 above are the one worth to mention.
hope this help.
CHEERS!
Click to expand...
Click to collapse
can u tell me, what works and what didnt work, in these androids???

Most stable for Polaris
Hi,
I always testing any incoming releases.
I vote for Incubus Froyo (RLS13 yet). If you don't use lot of screens, widgets, than it is the most stable for daily use. These things are the most important for me and they are work:
- Incoming calls come fast
- Data plan works: Task, Calendar, Contact
- BT carkit works
- Battery: I use sometimes pcarvalho lastest winmo and it drains battery more, than Android.
I think the most freezes are about the low free memory. But I'm on it to get more memory. If I use app and data on SD, I got max 40MB of free memory.

Hey, I got the same impressions of the Incubus RLS13, very stable BUT suffers from a memory problem... well, can't expect too much from the Polaris RAM when compared to the new devices in the market.
However, can u guys tell me if the Launchers (PRO and ADW) should make the phone slower (choppy)? I decided to stay with the stock launcher, apparently works better (apps, screens in/out), but I checked that PRO and ADW don't use a lot of memory.
For example, Tjahjo07, when u say keep the launcher in memory and 1 screen only, which launcher are u referring to?
Cheers!

@grgomes
he means launcher pro.

Tks Phyt. Yeah, I did try the speed-up suggestions, my Pola100 is much faster now.
2 screens LP, keep in memory, people widget and weather only. Minimal freeze and FC so far.
I did however go back to Liquid's 16/07 nbh, the 26/07 from DZO was giving me a lot of charging and booting issues. Seems much more stable now.
Im waiting for a Pola version for the 24/08 nbh from DZO, read some good reviews from people using Vogue...

I flashed Incubus26jc's Super Froyo (RLS14), Kallt_kaffe VaniljEclair RLS11 (CM5.0.8), Myn’s Warm Donut - [RLS 5], but there is no-one can run in my Polaris smooth.
My suggestion is don't install Android in your Polaris for business. Otherwise, maybe you will loss order or job.
Good Luck Everybody!

VaniljEclair
Use the VaniljEclair an reduce the pages of ADW.Launcher to 1! It works really fast!!! Ive got Pola200. If i flash Incubus Froyo WLAN dows not work. Running the other ROM everything works fine!!! I had 1.6 myns warm donut before. It had benn run from SD Card. By flashing Eclair I got a 2.1 which works as fast as Donut from SD card. Try it! Its great!!!

F1 plz
i read this guide : sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsNand
step by step done, but after install hardSPL, when i'm pressed CameraButton and Reboot, see the tricolor page , and nothing happen. what can i do ?!

@moapz: oh my god .. take a breath, you have posted in all the topics. wait a minute. someone will answer you. i think you are not doing something well. i have did that tutorial some time ago and had no problem with it. it would be better for you to try to install in haret mode first.
Have a nice day.

i have a problem to, when is the bars on the phone what i have to do? i need a program to flash the nand polaris? please help

Trak-X said:
@moapz: oh my god .. take a breath, you have posted in all the topics. wait a minute. someone will answer you. i think you are not doing something well. i have did that tutorial some time ago and had no problem with it. it would be better for you to try to install in haret mode first.
Have a nice day.
Click to expand...
Click to collapse
thanks TrakX.
i installed android NAND on my pola200 and worked. but after some days it goes crazy and according to this forum thresd i could remove old version and now i want to install another stable version, so i read wiki page but all links not worked! or say file not found. so i'm going back to read threads again to find what version is good. but another problem! ; many of this guides uses haret.exe to install android but i cant do this, because i don't have WM on my pola200 to run it. so can you help me for that? how to install new android ?

.

It seems that contributing to LOS building ROM is not anymore tolerated, this post is deleted.

Maybe @Scavenger87 wants to take a look here ;-)
I guess it's better to have an own dedicated thread.

Thanks for setting up a distinct thread. Things were getting confusing!

john_matrix said:
Maybe @Scavenger87 wants to take a look here ;-)
I guess it's better to have an own dedicated thread.
Click to expand...
Click to collapse
Hey John great idea with opening a new Thread because i also think its really confusing already
john_matrix said:
@Scavenger87: Steel01 advised to let 15.1 (I think he is right because it's too old and because lot of changes have been done between 15.1-16.0)
Also have found this during LOS 16.0 debugging and when application is crashing:
Starting from Android 9, LMK can be implemented in userspace and needs new optimization settings:
Low Memory Killer Daemon | Android Open Source Project
source.android.com
Will see if this new userspace LMKD can be tuned.
@Trevor_g: can't say... I don't have an Nvidia controller to test.
Click to expand...
Click to collapse
Ok yeah i think he's right for multiple reasons
- 15.1 had still unsolved issues aside of broken omx like the crashing nv games app and not working screen mirroring which is working so far on 16.0
- 16.0 is Android 9.0 based which is the same as the actual Software for the Shield TV. That means there is maybe a chance they can use some Codes or even Apps like the Shield Accessories to makes things like the First Controller working again over WIFI.
I even found a lot Nvidia OEM Apps here on APK Mirror : https://www.apkmirror.com/apk/nvidia/
I think i start testing around with those apks as soon i installed the lasted 16.0 build
@Trevor_g
For your question i have to check that again on 16.0 with the old Controller but i think its still only working over a OTG Adapter.
Like i mentioned above maybe the Shield TV Accessories App is working.
mirhl said:
https://gist.github.com/webgeek1234/8ef1bd105d2add3aa9c29028c2befbb0
https://github.com/vartom/drivers-kernel-nvidia-49/tree/smaug49/drivers/hid
https://github.com/devmapal/nvidia-shield-controller-driver
Click to expand...
Click to collapse
Someone even mentioned this Linux Driver for the Controller
But to be honest dont suspect too much on lets say all this bonus functions because first the LOS Team have to work on the base build to make it stable and running right

Ok i installed the latest build (4/1/21) yesterday on my LTE Tablet over sideload because i had no extra SD Card to format it to FAT32 and with the new TWRP 3.5-9.0.
I installed also the Pico Gapps and then TWRP said when i was about to Restart that there's now OS installed.
But thats seems to be a bug with TWRP itself because after the restart there was the LineageOS screen waiting for me and after a freeze for about a minute or two i was able to complete my installation.
After this i now can say its the most stable LOS 9.0 Rom so far !
It has very less apps crashing so far i only had to start them twice sometimes and also the hw acceleration working now most of its time at Chrome and on the Youtube App.
I can really see there has going again a lot of work into this Rom and its really a pleasure now to see how it get more stable everytime.
Big thanks to @Steel01, @npjohnson, the whole LineageOS Team and of course to @john_matrix
Btw @john_matrix did you change anything on the partitions you mentioned earlier on this build ?
@Trevor_g
I did a short test yesterday with the controller and as suspected it doesnt recognize by the tablet. I soon test out those Android 9.0 based Accessories App from the Shield TV

Thank you for the rom
Can I just flash this over Lineage 14.1 or do I need a factory wipe?
Did anybody test gamepass streaming yet?

danielandross said:
Thank you for the rom
Can I just flash this over Lineage 14.1 or do I need a factory wipe?
Did anybody test gamepass streaming yet?
Click to expand...
Click to collapse
Yes you have to wipe the device first in TWRP to install this rom.
Maybe a little general guide for everyone here who want to try this build in this early state and help tracking bugs
For an clean Installation its important to wipe the device first with TWRP like shown on the first Screenshot.
After this go to Advanced and choose everything choosen on the second Screenshot.
Now you shutdown the Tablet and insert the SD Card or plug in the cable for sideloading.
After turning on the Tablet and choose Recovery Mode again, first install the Rom of course then choose Wipe cache/dalvik.
Now you have to install Gapps if you want to use it. Its recommend to use only the Pico Package.
Wipe cache/dalvik again and restart the device.
If you use Sideload it might says in the Shutdown Menu :
No OS installed !
Which is a bug in my opinion of the new TWRP 3.5-9.0 Package but please use this Version of TWRP in any case that the basement of the installation is everywhere the same !
This is IMHO the way to install a Rom in a clean way and helps tracking down bugs better when everyone used the same methodes.
@john_matrix
I installed the Rom today on a K1 16GB with the methode i described above and did it with my regular SDCard i use in all my Tablets. In comparsion to installing over sideload it didnt get the No OS installed! message at TWRP and i didnt had that 1 minute freeze at begin of the install-wizzard after the LOS Logo.
Also the Rom seems to be same stable as the one on the 32GB model.
But i have to test it a bit more side by side to make valid statements
Also Nvidia Games working nice as you can see on the Screenshots

Hi guys, so, long story short i got scammed on a dutch advertising portal and ended up with one of them shield tablets which were recalled a few years ago. Yep, those with the defective battery that may burst in flame one day
Anyways, i figured that since it hasnt happened until now, i might just be lucky and give it a shot.
Its great to see that there is still some active development of this device! flashed this rom and i gotta say im positively surprised. Its running nice and smooth and even though it crashed on me a few times after the first boot, but a few reboots later and its running like a charm! i didnt bother with gapps, root or anything yet though. really great job devs!

Scavenger87 said:
I installed the Rom today on a K1 16GB with the methode i described above and did it with my regular SDCard i use in all my Tablets. In comparsion to installing over sideload it didnt get the No OS installed! message at TWRP and i didnt had that 1 minute freeze at begin of the install-wizzard after the LOS Logo.
Also the Rom seems to be same stable as the one on the 32GB model.
Click to expand...
Click to collapse
My tablet was completely wiped with no OS so I just pushed the ROM, pico gapps, and magisk over USB onto internal storage with MTP/TWRP. Flashed it all from there and it worked fine. No issues or errors. I don't think it's at all necessary to sideload to use an external SD.

Jackill said:
Hi guys, so, long story short i got scammed on a dutch advertising portal and ended up with one of them shield tablets which were recalled a few years ago. Yep, those with the defective battery that may burst in flame one day
Anyways, i figured that since it hasnt happened until now, i might just be lucky and give it a shot.
Its great to see that there is still some active development of this device! flashed this rom and i gotta say im positively surprised. Its running nice and smooth and even though it crashed on me a few times after the first boot, but a few reboots later and its running like a charm! i didnt bother with gapps, root or anything yet though. really great job devs!
Click to expand...
Click to collapse
In this Thread beginning from here i share my informations so far about the two type of batteries and changing them out if you interested:
Finding Replacement Battery in 2017?
Anybody know where to find a battery that will fit in the Shield Tablet? I know there are several threads online (here on xda, on GeForce forums, and other places) that discuss replacing the shield tablet battery and a few different part numbers...
forum.xda-developers.com
airtower said:
My tablet was completely wiped with no OS so I just pushed the ROM, pico gapps, and magisk over USB onto internal storage with MTP/TWRP. Flashed it all from there and it worked fine. No issues or errors. I don't think it's at all necessary to sideload to use an external SD.
Click to expand...
Click to collapse
I did these two type installation because @john_matrix mentioned to use a SD Card which is formated with FAT32 instead of exFAT. I didnt had one lying around so i used sideload this time.

Thank you everyone and Scavenger87 for your feedback! ;-)
About stability, I guess the culprit is the fact I have played with the new userspace LMK but for me it's not stable enough to be used as daily.
For example, Youtube often continue to play videos greeny and blocky and this is annoying
I will try to fine tune the best settings for LMK.
About battery, I have changed mine too with this one:
https://fr.aliexpress.com/item/32807531204.html
It works good but require to use the board of the original battery.

Seems to be going well so far for me, battery life seems good and for the general use I have had time to do it's worked well.
One crash that caused a reboot, after testing the hdmi output the tablet rebooted when I unplugged the hdmi cable from the tablet.

john_matrix said:
Thank you everyone and Scavenger87 for your feedback! ;-)
About stability, I guess the culprit is the fact I have played with the new userspace LMK but for me it's not stable enough to be used as daily.
For example, Youtube often continue to play videos greeny and blocky and this is annoying
I will try to fine tune the best settings for LMK.
About battery, I have changed mine too with this one:
https://fr.aliexpress.com/item/32807531204.html
It works good but require to use the board of the original battery.
Click to expand...
Click to collapse
Ok that means there is still some kind of memory leak problem with our tablets or is the memory managment on android 9 and higher not really suited for our low ram devices ?
I also read something about drawbacks with the in-kernel LMK as you can see here :
Drawbacks of in-kernel LMK driver
Android deprecates the LMK driver due to a number of issues, including:
Low-RAM devices had to be tuned aggressively, and even then would perform poorly on workloads with large file-backed active pagecache. The poor performance resulted in thrashing and no kills.
The LMK kernel driver relied on free-memory limits, with no scaling based on the memory pressure.
Because of the rigidity of the design, partners often customized the driver so that it would work on their devices.
The LMK driver hooked into the slab shrinker API, which wasn't designed for heavy operations such as searching for targets and killing them, which slowed down the vmscan process.
Is the zRam function now activated by standart on Android 9 and higher to compress amount memory is needed ?
I try to stresstest it today with a website that have a lot pictures sadly i cant use instagram anymore because you need a account now

Shield Tablet can't be considered as a "low ram device" as Google defined them with up to 512MB (Android Go?)
Android Performance Optimization | Android Open Source Project
source.android.com
I also have devices with 2GB that are currently performing Lineage 17.1 very well (Sony Z3C and Nexus 4)
I don't know if zRAM is activated by default in Android but you still have the choice to activate it or no (in the kernel or in the fstab.
Additionnally, I don't know what is the policy to activate zRAM (my Mi9 have 6GB RAM and have zRAM activated by Xiaomi so...)
Another thing about zRAM is there are lot and lot of options you can activate such as compression, lz4, clear caching, etc... depending of your needs and I am not skilled enough to say exactly what will be the consequences of these options (but it cost nothing to try).
You also have to keep in mind that zRAM will consume more CPU times (as KSM).
Similarly, you can fine tune the CPU governor and IO scheduling (often I see CFQ by default but on the other way I have saw that Noop and Deadline gives best results).
Feel free to share your experience and if you have other ideas on what you would like to integrate in this ROM (as the best possible).
You are right to stress test the OS, you can also debug the memory and the weight attributed on the processes.

Ok but 2GB is really not much these day also this article from android source is really old i think i read there something about kitkat or so
But your right i also was suprised to see that my xperia z3 compact i have lying around is able to run lineageos 17.1 and even is supported by the LOS Team
Which leads me to the question is the memory managment on the Qualcomm SOC so much better ? Ok the Ram there is on the SOC itself instead of external like on our Tegra based devices.
I think i install tonight Triodexes 15.1 with zram to compare the effect it has.
I also noticed the hw acceleration crashes the most on the firefox browser like i told in the 15.1 Thread you can start one video and it runs if you leave everything untouched but your not able to start a second one even with autoplay.
Btw about the LMK i know its maybe a dumb question but did you try the original settings from the Oem Rom ?
Edit : The original values in minfree are: 18432,23040,27648,32256,36864,46080
And zRam is already activated on the LOS 16.0 Build with 511MB same like the oem rom

Scavenger87 said:
I did a short test yesterday with the controller and as suspected it doesnt recognize by the tablet. I soon test out those Android 9.0 based Accessories App from the Shield TV
Click to expand...
Click to collapse
Thanks SO much for looking into this for me! You mentioned later that the controller wasn't recognized by the tablet, however I'm also curious if the Accessories app from the ShieldTV might help. Thanks again, in advance!

Fwiw, there's a bunch of framework patches needed for the wifi direct controller to work. I've yet to get them all straight. Haven't had that working since cm-12.1. See the incomplete set for 16.0 here:
https://review.lineageos.org/q/topic:shield-blake-p
That's on top of:
https://review.lineageos.org/q/topic:nvidia-shieldtech-p
And there's no nvidia pairing app that works with a touch interface. It's a mess atm. I did get blake to pair to foster on 15.1, but only while the pairing wizard was open. As soon as I hit back to close it, the autonomous group goes down and the connection is lost. And now, it's close to impossible since nvidia didn't release the nvwifi prebuilt jar to link against. And the one from O doesn't work on P.

Hi @Steel01
Thank you for keeping us updated on your work with the controller and also for your work for this device in general
I already tought its not easy to bring wifi support back for the old controller but i think also there is no high priority since the second gen is working fine over bluetooth and they already cheap to buy used.
Other than this the rom is suprisingly good running for this early stage and most of the stuff is working
Is there something that needs special attention for testing at the moment to help you developing ?
Like i mentioned in a other Thread i have every generation of the Shield Tablet and Controller. Only on my LTE Modell the SIM Card Reader is unfixable broken
But i still hunting for a fully working device.

Before I flash this Rom: Why do I habe to wipe internal storage?

danielandross said:
Before I flash this Rom: Why do I habe to wipe internal storage?
Click to expand...
Click to collapse
Well i dont know if its really needed to wipe the internal storage but i think by the reason we testing here a new Rom in a really early stage we should give it the cleanest basement as possible to exclude problems that might caused by left over data that interference with the Rom