I don't even have this phone, but I'm tired of hearing you guys complain about your wifi dropping . HTC programmed the Desire S to drop wifi connections if the signal falls below -88db. I'm not sure why they did that because -88db is a perfectly usable signal. With this fix, your wifi connection won't drop until the signal falls below -108db.
You need to be running a custom deodexed ROM to apply this fix.
Flash through Clockwork Recovery.
Let me know if it works for you!
If you appreciate my work, donations of any amount are very much appreciated.
Small update... noticed that I didn't set the permissions right on one of the files. May want to grab v2.
On another note, where is everyone? Dev community for this phone needs to wake up!
gtg465x said:
Small update... noticed that I didn't set the permissions right on one of the files. May want to grab v2.
On another note, where is everyone? Dev community for this phone needs to wake up!
Click to expand...
Click to collapse
i´m here ;-)
just downloading v2 and give it a go and a test...
i will report back as soon as i feel there is something happening after flashing ;-)
thanks for this.... if this works, i can enjoy my wifi in the kitchen while drinking coffee ;-)
regards and thanks
We still can't use it, for the majority of Desire S user got an S-ON units.
For those who can't apply the above fix due to "S on" (pretty much everyone?) you can try the easier way which I've posted in another thread. Some people said it doesn't help but there's no harm in trying
there's a stock setting that can enable Desire S to hold Wi Fi connection a lot better. Go to Settings -> Wireless & networks -> Wi-Fi settings. Click menu button and choose Advanced. Second section from the top is "Best Wi-Fi performance" - tick it. That's it. It really made the difference for me. Dropped Wi Fi signal was a frequent thing with my Desire S but ever since I've ticked this option (~1 week ago) I haven't had such problem at all.
rubbish said:
For those who can't apply the above fix due to "S on" (pretty much everyone?) you can try the easier way which I've posted in another thread. Some people said it doesn't help but there's no harm in trying
there's a stock setting that can enable Desire S to hold Wi Fi connection a lot better. Go to Settings -> Wireless & networks -> Wi-Fi settings. Click menu button and choose Advanced. Second section from the top is "Best Wi-Fi performance" - tick it. That's it. It really made the difference for me. Dropped Wi Fi signal was a frequent thing with my Desire S but ever since I've ticked this option (~1 week ago) I haven't had such problem at all.
Click to expand...
Click to collapse
Just so people know, doing this does NOT have the same effect as applying my fix. That might help you a little in the mean time until you get S-OFF, but my fix should completely fix the issue.
Also, why does loveboatcaptain appear to have S-OFF and the rest of you can't?
^^^^^^^^^
He might used xtc clip to turn it from s-on to s-off
this is the only way to do this until a dev figur some
software way to do this
abo.saud said:
^^^^^^^^^
He might used xtc clip to turn it from s-on to s-off
this is the only way to do this until a dev figur some
software way to do this
Click to expand...
Click to collapse
Yes, true, and the xtc-clip is pretty expensive too, so most of us have to wait for a software method to get s-off, and then we can root and install clockworkmod i believe.
Unless you knew someone or somewhere who can make it to S-OFF, cause the xtc clip is expensive.
Why there are two files to dowload? What's the difference?
Anyway: thanks for the fix
Now there would be a reason to flash the deodexed ROM from loveboat
As there are few devices sold and there is only one cook but no "hardcore-devs" (no offense to loveboatc.) for kerneltweaks or S-off there is not much life here..
Mine is S-off since SIMunlock - but done by a company for money (EUR 20,-)
But the stock-htc-2.3.3 is really great (very good battery, very stable,...) - so better than CM7 on my NexuS :/ I only needed root for deleting the htc-ads.app (navigation, amazon,...) and for adblocker,..
dont know said:
Why there are two files to dowload? What's the difference?
Anyway: thanks for the fix
Now there would be a reason to flash the deodexed ROM from loveboat
As there are few devices sold and there is only one cook but no "hardcore-devs" (no offense to loveboatc.) for kerneltweaks or S-off there is not much life here..
Mine is S-off since SIMunlock - but done by a company for money (EUR 20,-)
But the stock-htc-2.3.3 is really great (very good battery, very stable,...) - so better than CM7 on my NexuS :/ I only needed root for deleting the htc-ads.app (navigation, amazon,...) and for adblocker,..
Click to expand...
Click to collapse
The two different versions are for two different ROM bases. Look in your software information to see which firmware you're running.
gtg465x said:
Also, why does loveboatcaptain appear to have S-OFF and the rest of you can't?
Click to expand...
Click to collapse
yes i used the xtc clip to get s-off, but didn´t buy one. i found someone who has this clip in a german android forum. meet him, give him some bugs (15€) and a coffee and while drinking that coffee he unlocked my wildfire and my desire s.
so you needn´t to buy it, cause you only will use it once. the s-off with the xtc clip is irreversible. nothing what you can flash can change that at the moment.
there is a second possibility with the clip as i read. there is a new version for sale which works "prepaid" and costs something like 25€/20£ which is a quite cheep way to get s-off i think.
phone repair shops in berlin for example have that clip too. will take some time to find one, but it´s really simple when you live in a bigger city.
dont know said:
Now there would be a reason to flash the deodexed ROM from loveboat
As there are few devices sold and there is only one cook but no "hardcore-devs" (no offense to loveboatc.) for kerneltweaks or S-off there is not much life here..
Mine is S-off since SIMunlock - but done by a company for money (EUR 20,-)
But the stock-htc-2.3.3 is really great (very good battery, very stable,...) - so better than CM7 on my NexuS :/ I only needed root for deleting the htc-ads.app (navigation, amazon,...) and for adblocker,..
Click to expand...
Click to collapse
grrrrr ;-) i know that i´m not a hardcore dev :-( sadfully for myself too.
i would like to have someone who can do the job better than me. i made that only for myself, but wanted to share that with the community, cause there was nothing really usefull to find. and without HCDR.Jacob we would still have nothing, cause i would have failed on that what we now have.
give me some more time. i´m a hardcore family father, with a 10 month old little boy and a wunderfull wife, who like what i´m doing in my freetime, cause she´s addicted to android too *chear* and of course i have a fulltime job too.
but i´m working hard in my freetime to build something that will be a good basement for evrything that comes further.
on my next 2 or 3 free days i will be have a look at the kernel. perhaps HCDR.Jacob will give me a hand on that again, so we could do a little OC and UV for better battery life and some smartass-gov tweaks.
i also set up my mac (yes shame on me i use an apple macbook to build android ;-) ) to build from source for android.
you know what that mean right? AOSP ROM ;-) or to be clear CM7 !!!
but this will take a lot of time i think. for me ;-) but let´s see what i can do for all of use until there are hardcore devs around. which would be super cool to have someone to work with...
regards
im a new android user, i booted into the clockwork thing and selected your update file from sd card to update with. It appears to install correctly.
Is there a way i can check if this patch has been installed properly or not?
Thanks
bongo1 said:
im a new android user, i booted into the clockwork thing and selected your update file from sd card to update with. It appears to install correctly.
Is there a way i can check if this patch has been installed properly or not?
Thanks
Click to expand...
Click to collapse
Open /system/etc/calibration as text and see if rssi_offset at the bottom of the file is equal to -20.
Sent from my Inspire 4G using XDA App
Thanks for that, my offset is 0 so didn't work, does the patch work on the stock eu firmware with root, or do I need to use loveboats custom firmware?
Thx
Sent from my HTC Desire S using XDA App
Installed loveboats custom firmware,
maybe i missed something but i did following.
- install LBC MOD SAGA alpha v0.01
- boot into clockwork recovery
- select install zip from sd card and select saga_wifi_fix_1.28.401.1_v2.zip
- install sucessfull
- reboot phone
- rssi_offset=0 so did not work
did i make any mistake?
thanks
bongo1 said:
Installed loveboats custom firmware,
maybe i missed something but i did following.
- install LBC MOD SAGA alpha v0.01
- boot into clockwork recovery
- select install zip from sd card and select saga_wifi_fix_1.28.401.1_v2.zip
- install sucessfull
- reboot phone
- rssi_offset=0 so did not work
did i make any mistake?
thanks
Click to expand...
Click to collapse
so i found time to test your fix a little bit...
sadfully i have to say that your update.zip didn´t work with my ROM (see below).
the files are working, really gread... now i can drink coffee in my kitchen without loosing my wifi connection. thank you very much for fixing that.
to fix your update.zip i compared your updater-script with mine.
you used the following mount command:
Code:
mount("ext3", "EMMC", "/dev/block/mmcblk0p26", "/data");
mount("ext3", "EMMC", "/dev/block/mmcblk0p25", "/system");
i used this:
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p26", "/data");
the desire s and the incredible s are using ext4 which you can find out by typing following in your terminal:
Code:
adb shell
mount
this is the output from my terminal:
Code:
...
/dev/block/mmcblk0p25 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p27 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p28 /devlog ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
...
i´ve had the same problem with my ROM and while compiling and building the clockworkmod recovery... after changing everything to ext4 clockworkmod and the script installed my ROM successfully.
i tried the lines and modified your script and after that the files where changed correctly.
hope that will help the other ones having problems to flash it.
regards
p.s. can i use your fix in the next update for my ROM (credits included ;-) !! ) and is it possible to increase the values a little more (just for personal interest)
i can confirm changing the file system as you suggested worked
Thankyou to both.
Thanks loveboatcaptain. I just assumed the mounts would be the same as the Desire HD. Updated the fixes in the first post to mount ext4.
Related
WARNING:You must Have The Correct Radio and Latest SPL! You can find them here (RADIO MUST BE INSTALLED FIRST) You can find it here
PLEASE DO YOUR RESEARCH BEFORE FLASHING ANY ROM INCLUDING MINE IT WILL SAVE YOU AND OTHERS TIME AND HEADACHE!!!
First A big thanks to Haykuro for providing the system dump of the latest known Hero build. Great contributions from Haykuro always!!! Make sure to thank him!!!
This ROM is based off the latest "HTC" ROM leak 2.83.x.x with tons of mods enjoy!!
This is the same as the build posted in the dream section,we just wanted to keep the two threads clean so all MT3G/Sapphire Q: and problems should be posted here. As of now it works only on 32B but 32A kernal is being worked on so will be coming soon give ccyrowski time he is working hard for us.
NOTE: Once you flash before you sign in do the led fix in the instructions,also we recommend using ext3 and a 64MB Linux-swap partition.
JacHEROSki 2.2r4 Remix More Specs Coming!
Fix Video audio
Added lastest tether 1.60
Added Sapphire folder
Added the new LED app By jinx10000
JacHEROSki-v2.2 - Experimental A & B
A
-2.6.29.6-jac-ski [email protected]
-BFS 240
-supports MyTouch out of the box!
-MT
-various ramconsole and usb patches
-other things I can't think of
B
-same as A with the 10MB RAM hack (10 extra MB of RAM)
-other things I can't think of
Install Instructions
First using adb I remove the ext3 and linux swap if you have them set already like this, remember the numbers will vary with the size of you card but I will show mine as an example.
In Recovery
This Removes the partitions
adb shell
parted /dev/block/mmcblk0
rm 2
rm 3
This makes the partitions ext2 and linux-swap 64MB remember numbers vary according to the size of your S.D if your not sure ask first.
mkpartfs primary ext2 3767 3901
mkpartfs primary linux-swap 3901 3965
This upgrades the ext2 to ext3
quit
upgrade_fs /dev/block/mmcblk0p2
Now with the build on your S.D
Wipe
Flash the build A or B
Now once the build loads up you may get a FC on HeroLED.apk which there is a fix that I know of for MyTouch but cant be done because the sapphire folder is not in the build and not needed the HeroLED.apk is not needed since they work without it.
Phone on as normal
Fixing the HeroLED.apk
Fix the FC on HeroLED.apk and also get your phone to read as a Magic/MT3G.
Terminal
su
rwsystem
magic
reboot
Click to expand...
Click to collapse
This is how I install my builds and have it running as smooth as I do if your not sure you can do all this don't try. I do it and my phone runs sweet, but I will not take blame for people messing up there phones because they don't know what there doing.
JacHEROSki 2.2r4 Remix: http://www.4shared.com/file/136918974/b6e7bf4c/jacheroski22r4_Remix.html
JACxHEROSki-v2.2a: http://www.justanotherdev.slackdev.com/jacheroski2.2a.zip
JACxHEROSki-v2.2b: http://www.justanotherdev.slackdev.com/jacheroski2.2b.zip
Good **** thanks manup. Will you be adding BFS-300 to this tonight?
Omg...cant wait for 32a version ....STILL !!!!!
rebooting with new remix rom
I am getting frequent reboots ( about every 30 minutes) and also am getting a force close due to leds any ideas?
oops
I found the fix for the led force close. any idea on the rebooting?
Well the rebooting I have not seen on these ROMS really I would reflash again and let me know if still keeps happening,also are you using the remix or what version?
@jabbawalkee
I will maybe drop tonight not sure its up to cc but the BFS-300 will have the 10MB hack for MT3G/Magic for those who dont know that. I know you do but some are waiting so I tossed that info in there.
@Daneshm90
I know bro I am working on getting that for you hopefully today but cc is a bit under the weather so we will see.
manup456 said:
Well the rebooting I have not seen on these ROMS really I would reflash again and let me know if still keeps happening,also are you using the remix or what version?
@jabbawalkee
I will maybe drop tonight not sure its up to cc but the BFS-300 will have the 10MB hack for MT3G/Magic for those who dont know that. I know you do but some are waiting so I tossed that info in there.
@Daneshm90
I know bro I am working on getting that for you hopefully today but cc is a bit under the weather so we will see.
Click to expand...
Click to collapse
Thanks man. I have 300, but wasn't working too well when I flashed it as an update over A...may try deleting/recreating my partitions and re-trying it.
Not sure bro I have been using it since yesterday on a fresh fromat and install and its been really good for me so yeah I would def give a fresh format and install.
manup456 said:
Not sure bro I have been using it since yesterday on a fresh fromat and install and its been really good for me so yeah I would def give a fresh format and install.
Click to expand...
Click to collapse
Are you using it on A or B?
No I use a whole ROM with it built off of 2.2r4 thats what I thought you had P.M me to see what it is your using.
manup456 said:
No I use a whole ROM with it built off of 2.2r4 thats what I thought you had P.M me to see what it is your using.
Click to expand...
Click to collapse
Check your box
Great work.
After seeing that Tweet from last night. I'm glad to see this up-and-running this afternoon.
About time the "official" build finds a home in the Sapphire Development Section.
Oh, and thanks for the hard work put in last night. I was working like a dog, testing for CC last night on that BFS-300 patch. Lol.
(not that it was "hard" work or anything.)
Glad to see you in this section though.
No prob I will be around in both sectitions because I have both G1 and the MT3G,I wanted it to not be so mixed in the dream thread people seemed to get confused there will be a update either today or tommarrow that will be real nice.
I am helping as much as I can but cc is killing it with all his new work and mods mike's user.conf is also amazing.
manup456 said:
No prob I will be around in both sectitions because I have both G1 and the MT3G,I wanted it to not be so mixed in the dream thread people seemed to get confused there will be a update either today or tommarrow that will be real nice.
I am helping as much as I can but cc is killing it with all his new work and mods mike's user.conf is also amazing.
Click to expand...
Click to collapse
Take your time tonight.
You might as well drop tomorrow, just give everything a chance to settle today.
People are hyped enough on the BFS-300 high. Lol. No need to cause a global overdose.
I'm eager to see this user.conf you speak of. Some sweet-ass options within I hope! As for the G1 and MyTouch, same here. But, I have three MT3G devices. (employee of; you guessed it.) Anyway, if you need a tester later tonight or whatev.
TWEET ME!
US MT3G w/2.2a problems
First, I have an 8GB SD card, with the standard partition sizes (7GB FAT32, 32MB Linux-Swap, and the rest Ext3)
I am using Cyanogen 1.4, and I did a wipe, and check of my ext before updating. The SD card was empty on all partitions, except the 2.2a named as update.zip
First thing I saw on startup (and every startup) is the LED notify crash, but more serious is the phone being stuck in headset mode. Tried rebooting, plugging in charger, plugging in actual headset, but it was just stuck on.
I ended up flashing back to my stock tmobile 1.5 firmware until it's more stable.
My knowledge of this device is a bit limited at this point. I know I am running the latest radio, but I am not clear on what SPL is (or ADP for that matter).
Can anyone help fill in the blanks or tell me what I am doing wrong?
tia,
-dana
I said in the first post that swap is better at 64MB and there is instructions in the first post that talks all about the FC on HeroLED all you need to do is hit o.k and follow the steps posted. Also coming from another wipe a format of the ext3 should have been done read the first post.
Does everyone have the auto-backlight option?
Same issues...
manup456 said:
I said in the first post that swap is better at 64MB and there is instructions in the first post that talks all about the FC on HeroLED all you need to do is hit o.k and follow the steps posted. Also coming from another wipe a format of the ext3 should have been done read the first post.
Click to expand...
Click to collapse
Thanks for pointing that out, I now see the instructions that I did not notice before.
I used Ubuntu to delete my partitions, and re-do them with the sizes stated in the instructions, so the partitions are clean. I then copied the update.zip (22a) to the card, and put it in the phone. Started Cyanogen, wiped, repaired ext partition, and installed the update.zip
I still have the headset indicator stuck on.
Went into terminal, but could not get a keyboard to come up. I used "better terminal emulator" instead, which should work. I followed the steps, but when I got to "magic", it came back with "rm failed for system/bin/sapphire, no such file or directory"
I still have the LED FC at startup, and am still stuck in headset mode.
Any ideas?
tia, again,
-dana
dleasman said:
Thanks for pointing that out, I now see the instructions that I did not notice before.
I used Ubuntu to delete my partitions, and re-do them with the sizes stated in the instructions, so the partitions are clean. I then copied the update.zip (22a) to the card, and put it in the phone. Started Cyanogen, wiped, repaired ext partition, and installed the update.zip
I still have the headset indicator stuck on.
Went into terminal, but could not get a keyboard to come up. I used "better terminal emulator" instead, which should work. I followed the steps, but when I got to "magic", it came back with "rm failed for system/bin/sapphire, no such file or directory"
I still have the LED FC at startup, and am still stuck in headset mode.
Any ideas?
tia, again,
-dana
Click to expand...
Click to collapse
Get 2.2r4, not 2.2a
manup456 said:
Does everyone have the auto-backlight option?
Click to expand...
Click to collapse
No auto-backlight option after installing 2.2r4 and running the magic script.
A Very quick port of the Mytouch Slide Leak.
Credits : Vega, his files made it boot
Upload date 2010-04-22
Download at the bottom of this post
Very Quick 'status' list
Hangover edition v003c
WiFi - Fixed - honestly its fixed now
Market - Fixed - I know , I know , you have no reason to believe me
Theme Switching ( MyMode ) - Fixed
YouTube, sound no video
Gmail seems working, until you try to read one
Browser not working, stock or third party- looks like an issue with binder, this is what I want to fix next
the MyTouch Music player works
FullScreen weather - better , but sun 'shines' blue, idkw
Silly Bootanimation, - Replace by pushing to /data/local/bootanimation.zip
lots of other things untested/ not working
I'm sure that will be amended/appended
Main Features
MT3G friendly a2sd
CacheHack - 3 in 1 Flashable Zip
Auto swap ( you have a swap partition , it will find it and set it up )
AnySPL
[*]Eng/Hard/Stock aka NoneDanger
[*]Death/Haykuro aka Danger
[*]Any MT3G SPL
One zip does it all?
yeap,
I get the recovery program to run a shell script, this script looks at the size of mtdblock4 ( the 'cache' partition ) and then creates symbolic links based on what 'SPL' it has determined, then the rest of the ROM is flashed, the files follow the links and .. well its like someone sat down and thought about the best way to use the space
At some point I would like to look at getting that shell script generated so that it can very easy to apply to any rom.
Danger I do have to admit that the Danger version is a bit of a 'quick fix', around 20mb is idle on /system, I'll look at improving on that.
At the moment all the system apps are on data, but as app_IS, with a little bit of 'moving and re-linking' we can trigger a2sd to do its thing
Edit 2010-04-24: system apps are going to sd by default now
NoneDanger is as good as it can get on the G1, got a couple of mb free space on system, and that will likely improve as the 'bad apps' are weeded out
I currently have 37mb free on data, yeah I know for some reason people want this empty, why? its faster than sd
MT3G ok, so you don't have a keyboard , but space you have lots of space
The script will chop this 164mb rom in two and share it across /system and /cache leaving the 295mb /data partition free for dalvik-cache, user apps and setting/files
Download
######## MD5SUM ##########
#########################
72b53b0f3b16ea9e161e605b8dfe47d0
#########################
Uploading a new version
fingers crossed, working for everyone.....
FR-MTSlideTo32B-v003c-AnySPL_S.zip
NB, WiFi, themes (MyMode) and market
no browser yet...
#########################
Current Patches
###########
FR-FavesFix4-003c_S.zip
Should be able to flash straight after the main 'ROM', if it does fail, just reboot straight back to recovery and flash the fix again
#########################
Instructions !!
OK, this is a very early release, consider it Alpha, the ROM is Huge and as such it takes a good while for it to settle.
If you 'went in' a little early you will see FC's , and it will look real bad...
But trust me , its fine
Reboot by pressing call + end and then menu, and let it settle
One it gets settled in it actually does quite well, much better than I had hoped
and I have not done any tweaking yet, just got it to boot
Edit : 2010-04-24 - Its actually quite stable on a first boot now
But still give it a couple of minutes, and do the full sign in
( i.e. don't charge in to do a market sign in, never understood why that was needed )
Missing widgets?
probably 'logged in' a little too quick
if widgets seem to be missing, then
settings --> applications --> manage applications --> menu(key) --> filter --> all --> HTC sense --> clear data
should make them all available
Make Backups?
you need
[UTIL] BART-1.2.0 Backup and Restore Tool
Now supports backup and restore of CacheHack ROMs
Anyway, I hope you enjoy
feel free to use as a base,
32a Port - not confirmed working yet
Daneshm90 said:
Hey, any chance of a 32a port? thnx
Click to expand...
Click to collapse
Firerat said:
errm yeah
I'll have ago but I can't test
Click to expand...
Click to collapse
Firerat said:
FR-MTSlide-32a_S.zip
no idea if it works
Click to expand...
Click to collapse
Just a Kernel , so flash it last
A quick note on patching CacheHack ( or any ROM )
Just wanted to make a quick post on Patching this ROM, and any ROM for that matter
as stuff is on cache, and is in different places dependent on the SPL symlinks are are 'broken'
So, we fix them in the update script
mountall.sh
Code:
#!/sbin/sh
mount -a
if [ -d /system/csys ];
then
mount -o bind /cache /system/csys
fi
now, in your update-script the top line should read
Code:
run_program PACKAGE:mountall.sh
assuming that mountall.sh is in the root of the zip
now, when the update-script runs the mountall.sh
all partitions get mounted, and if /system/csys directory exists it bind mounts /cache to it
All of the symlinks will now work
so , if your replacing a file in /system/lib the link will be followed
Danger its actually /system/lib/
NoneDanger and MT3G its /cache/system/lib ( or /system/csys/system/lib )
this also means you can easily do
Code:
copy_dir PACKAGE:system
where in the zip
system/
system/lib/libWatstis.so
system/app/SomeSystem.apk
libWatstis.so ends up in the right place
as does SomeSystem.apk, even if its on the sd ,
( /system/app >> /data/app_s >> /system/sd/app_s )
in the past, to 'upgrade' a system app on sd, people would delete /data/app_s ( as it was a symlink ) which would break things for anyone not using a2sd
nb, the mountall script should be in unix format, else it will fail !!!
a third post
Silly edit is silly, will test out later.
So much win coming soon. Thanks for the post. Is the AnySPL a no-wipe from your first one?
I noticed I can't change scenes. Just does nothing-- is that me or a bug to be worked on? And the bloatware makes me think I bought an ATT phone all over again, lol. There's a lot of room for improvement. Just when I was getting bored with Legend, got a new toy to play with.
just checking before i get too far in this is the cfs-3d kernel on this rom already or do we flash that one over this rom also?
Let see
Giving this a try right now on my Mt3g... Will let you know how I go.
enatefox said:
So much win coming soon. Thanks for the post. Is the AnySPL a no-wipe from your first one?
Click to expand...
Click to collapse
Hmm, hadn't thought of that
/system and /cache get wiped by the script, but I leave /data alone
it might get touchy about it with no wipe
One of the things I want to do is the deal with the whole wipe thing, I personally don't wipe, if it works , if not then I wipe
do i still have to flash the kernel from the other post on top of it?
vortec87 said:
just checking before i get too far in this is the cfs-3d kernel on this rom already or do we flash that one over this rom also?
Click to expand...
Click to collapse
Oh, yeah, sorry its already got the CFS 3D
SmartBrother90 said:
do i still have to flash the kernel from the other post on top of it?
Click to expand...
Click to collapse
nvm i see the answer
Firerat said:
Oh, yeah, sorry its already got the CFS 3D
Click to expand...
Click to collapse
Thanks Firerat You are the MAN!
No incall volume...Looks really SICK!! Good job!!
this is for g1?
This will change your life. Run as root, thank me later
Code:
pm disable com.htc.htclocationservice/com.htc.htclocationservice.AutoSettingReceiver
pm disable com.htc.socialnetwork.provider/com.htc.socialnetwork.provider.SocialUpdateReceiver
pm disable com.tmobile.nabservice/com.tmobile.nabservice.NabSyncReceiver
pm disable com.tmobile.selfhelp/com.tmobile.selfhelp.BootCompletedReceiver
pm disable com.android.voicedialer/com.android.voicedialer.VoiceDialerReceiver
pm disable com.google.android.apps.maps/com.google.googlenav.friend.android.ServiceReceiver
pm disable com.htc.htclocationservice/com.htc.htclocationservice.AutoSettingReceiver
pm disable com.android.bluetooth/com.android.bluetooth.opp.BluetoothOppReceiver
pm disable com.htc.providers.uploads/com.htc.providers.uploads.UploadReceiver
pm disable com.google.android.apps.uploader/com.google.android.apps.uploader.common.ConnectivityBroadcastReceiver
pm disable com.android.voicedialer/com.android.voicedialer.VoiceDialerReceiver
pm disable com.tmobile.thememanager/com.tmobile.thememanager.receiver.ThemePackageReceiver
pm disable com.svox.pico/com.svox.pico.VoiceDataInstallerReceiver
pm disable com.android.voicedialer/com.android.voicedialer.VoiceDialerReceiver
pm disable com.htc.htclocationservice/com.htc.htclocationservice.AutoSettingReceiver
pm disable com.oz.mobile.android.voicemail.application/com.oz.mobile.android.voicemail.application.VoicemailBroadcastListener
pm disable com.htc.android.omadm.service/com.htc.android.omadm.service.StateReceiver
pm disable com.nuance.vsuite/com.nuance.vsuite.drivermode.MessageReceiver
pm disable com.tmobile.nabservice/com.tmobile.nabservice.SMSSyncService
u da man firerat! it works.
Thanks for this
Umm since there is no BootScreen how long does it usually take to boot ? because i am kinda iffy on weather i should wipe again and flash
(been booting for about 5 mins)
whats the diff between this one and the other slide rom?
This fast already...
Wow, I have no idea wether it's your Cache hack working well or that this ROM just works better with the mt3g but I can't believe this is the first release. Looking forward to everything working... Will use this as my everyday ROM for sure!.
XxKOLOHExX said:
Thanks for this
Umm since there is no BootScreen how long does it usually take to boot ? because i am kinda iffy on weather i should wipe again and flash
(been booting for about 5 mins)
Click to expand...
Click to collapse
logcat dude... ur a dev.
and it should be more than 5. it odexes on boot.
.: MarloFroyoBareBones :.
Cyanogen 6.0 RC2 - "ReCooked" Bare Bones Edition
Cyanogen's Thread
http://forum.xda-developers.com/showthread.php?t=722801
After ROM install: Available Space 67.74MB
After gApps install: Available Space 56.75MB
**** PLEASE READ EVERYTHING ****
**** I AM NOT RESPONSIBLE ******
Cyanogen's Pre-Req's Remain for this ROM
:::ROM = REMOVED:::
=Bluetooth.apk
=Browser.apk
=Calculator.apk
=Camera.apk
=DeskClock.apk
=Development.apk
=Email.apk
=Gallery3D.apk
=LiveWallpaperPicker.apk
=Music.apk
=PicoTts.apk
=Protips.apk
=RomManager.apk (I prefer AmonRa)
=SoundRecorder.apk
=SpeechRecorder.apk
=Stk.apk
=term.apk
=ttsservice
=voicedialer.apk
=vpnservices.apk
:::ROM = ADDED:::
=Gallery (Legacy Gallery, Not 3d)
=RealCalc (Full service Calc, not the basic one included)
=Cubed - Music Player
:::GAPPS = REMOVED:::
=Amazon MP3
=GenieWidget.apk
=googlevoice.apk
=kickback.apk
=soundback.apk
=talkback.apk
=talk.apk
=VoiceSearch.apk
I made this to my taste,
but thought I would share.
Most people have 3rd Party apps they use.
If options you need were removed,
this ROM may not be for you.
::: SD Setup :::
Swap
Fat
ext - optional - only has Froyo app2sd
::: TO INSTALL :::
- Do whatever you do for backing up, example: nandroid
- Wipe with this method:
---- While USB plugged to the computer,
---- run the bat in this post and format this way:
http://forum.xda-developers.com/showpost.php?p=6855422&postcount=3
---- to ensure full format, I also use AmonRa recovery wipe options
---- just to be safe
---- If you are comfortable in ADB, then just use it to run this command:
adb shell mount -a; rm -rf /system/*; rm -rf /data/*; rm -rf /cache/*;
---- You can skip the bat file if you do this
- Flash ROM ONLY
- Reboot Device
- After that, change whatever settings you would like. DO NOT INSTALL ANYTHING.
- Just Setup CM settings, wifi, etc (optional)
---- I like to enable wifi and put in my network key
---- so my wifi is going when the market begins
---- to sync my apps
- Reboot Recovey
- Flash GAPPS
- Reboot
- Unlock after reboot and you will be prompted with the Google sign in.
---- After unlock, I usually plug it in, have wifi enabled,
---- set it up under 'USB Debugging' to "stay awake when plugged in"
---- and leave it alone for a bit. This way, you aren't stressing out your system
---- while the market is downloading 100 apps at once lol
---- This is also why I reboot and setup PRIOR to installing gapps.
---- A reboot or three may be needed to ensure everything is settled in nicely
---- If you are wondering where your responsiveness is, look at your downloads
---- in the market, see if you are still syncing. If you reboot during some downloads,
---- you may need to cancel and restart them.
Fully Tested on my G1.
Current Phone Specs:
- Danger SPL
- G1-radio-2_22_23_02
- Dithering OFF (CM Options)
- 96mb Swap
- 512mb ext3 - just in case, this way, if I need an ext partition, I dont
-------------- have to re-format the entire card.
I am not responsible for any outcome
due to your use of this ROM in any way.
Use at your own risk.
Credits:
Cyanogen and everyone who built CM6RC2, as I used it as a base.
SpeedTeam : XxKOLOHExX
Relentless ROM Roaster - relentlessappz.com
ROM Kitchen
XDA Community
=========================================================
Marlo's ROM: http://www.mediafire.com/?mx2jmwxlcpemtnv
Marlo's GAPPS: http://www.mediafire.com/?tdwki25qghodu1d
no camera? :/
jewishjawsh said:
no camera? :/
Click to expand...
Click to collapse
Like I said, I use 3rd party apps for that.
I use Camera Zoom FX and mAPPn360
Those apps are much slower than the stock camera app imo. What's wrong with the camera app included in CM6? Snappy for me
jewishjawsh said:
Those apps are much slower than the stock camera app imo. What's wrong with the camera app included in CM6? Snappy for me
Click to expand...
Click to collapse
As I stated:
I made this to my taste,
but thought I would share.
Most people have 3rd Party apps they use.
If options you need were removed,
this ROM may not be for you.
If you want the app that bad, extract it from CM6 and install it on here.
Or, not use this ROM. Simple.
Great work Marlo, nice light ROM. Keep up the great work and I do appreciate your hard work and thanks for sharing your work.
Also appreciate the work on this Marlo!
Flashing now
You should call this No bloat lol
stlouie65 said:
Great work Marlo, nice light ROM. Keep up the great work and I do appreciate your hard work and thanks for sharing your work.
Click to expand...
Click to collapse
RandumAccess said:
Also appreciate the work on this Marlo!
Flashing now
Click to expand...
Click to collapse
Thanks guys. I appreciate your appreciation.
Zei said:
You should call this No bloat lol
Click to expand...
Click to collapse
I was going to leave the "nes" of Bones...
MarLo FroYo BareBo
So far, no hiccups on my end.
Yea great job now i don't have to do all this myself =]
Bloat-Freeeee
stlouie65 said:
Great work Marlo, nice light ROM. Keep up the great work and I do appreciate your hard work and thanks for sharing your work.
Click to expand...
Click to collapse
answr said:
Yea great job now i don't have to do all this myself =]
Bloat-Freeeee
Click to expand...
Click to collapse
I knew I wasn't the only one who didn't want all the other junk!
Hey marlo, I have a problem. I've never modded my g1 before and decided to do this rom first off. I went back and rooted it and then installed amon ra recovery and did radio update to 2.22 and danger spl.
I flashed your rom through recovery and it booted up fine the first three times but for some reason now it wont stop rebooting. It gets to the home screen, "press menu(my bad) 'swipe' to unlock", for about a second or two and then screen fades as if I did a battery pull. Then boots right back up.
I'm going to try some things when i get home, in recovery, when I wipe before install, am I suppossed to wipe all options in that sub menu? Any help would be much appreciated! Thank you and all others in advance.
Alright still having the same problem. I loaded in recovery and wiped everything except the sdcard partition, which I dont have my sdcard partitioned, so I didnt want to do it and wipe my rom zip.
After wiping everything else I reflashed the rom from sd. And rebooted from recovery. Rom loaded up great and worked perfect on first boot for about an hour until I decided to reboot it to make sure everything was working great and it started again.
Will load up to "swipe to unlock" and once its done preparing sd card it fades like I did a batt pull. Help, please?
Ok, sorry I wasn't following forum rules. I didn't know the meaning of the term "search". I spent a good 45 straight minutes searching just now as well as searching earlier today, but you guys are right, it pays off. I had wifi on, and only after a reboot would it go into the wifi reboot bug because on first launch with no wifi on it would connect without rebooting.
Hey marlo, I have some questions about this build and about a stripped down version of android to run games. Answer on here if you like, but I'll PM you about it.
Sorry for the delay. Your bug may have something to do with cyanogen, or what I removed. CM has been known to do similar things.
I never experienced your scenario, but I'm not saying I doubt you.
Games ran fine for me, I played robo defense all the time.
Thanks for trying my version of CM.
Sent from my SGH-T959 using XDA App
I wanted to use my old g1 as just a game machine. Do u think u can cook me a stripped down rom with the best attributes to run games?
Sent from my T-Mobile myTouch 3G Slide using XDA App
Browser
Hi Marlo , was just wondering how i get the browser back as everytime i install the browser.apk from CM6 it force closes. thanks,
appreciate the ROM as well , great job!
Twinny
Great Job
Great job Marlo. I like what you did with the Mod. Without all other stuff on there my battery last longer. Now i can add the .apk that i want.
Alright, noob here. Since I cannot post in the PACMAN development thread (http://forum.xda-developers.com/showthread.php?t=2164406) I will put this here.
- Problems installing PACMAN ROM
- After receiving "Errors Flashing", failures, downgraded recovery to TWRP 2.3.3.0
- 2.3.3.0 displayed "Error 7"
- Searching on error 7 led me down the path of the assert checks
- updater-script assert command in PACMAN ROM package is checking for model "ville".
- My HTC One S Special edition returns "villeplus" from "adb shell getprop ro.product.device"
My understanding is that the North American S4 and the Special Edition share identical hardware, only differing in drive size (16 vs. 64GB), so I am assuming any ROM designed for the ville will work on my phone.
Assuming it will I should be able to edit the "updater-script" file, but when I extract it windows is telling me that 23 files are duplicates. I'm not sure if this is because its windows vs. Linux that I'm extracting it on?? In any case, I don't seem to be able to modify the file without adversely affecting the integrity of the archive. Also would assume replacing the file will affect the MD5 hash which I believe TWRP checks when loading the ROM?
So first off, can someone confirm that this ROM will be compatible with my phone and 2, any suggestions on modifying the updater-script file within the archive?
Update
I was able to modify the updater-script file tonight using file X-Plore and text edit, so now the script is looking for "villeplus" rather than ville. My phone is S-OFF which I read means that it does not do signature checks... however, I'm not sure if that also means it bypasses MD5 checksums - I suspect not since I'm pretty sure I saw it verifying MD5 previously. So, since I tampered with the ZIP it still may not work.
My real question now that remains is even if it will work, do I want to flash a ROM built for the ville to my villeplus. The more I read about custom ROMs the more it appears that they are extremely specific to models.
I am still extremely curious to try it... rumor has it that curiosity didn't work out so well for the cat though. :-/
merovingian_a51 said:
I was able to modify the updater-script file tonight using file X-Plore and text edit, so now the script is looking for "villeplus" rather than ville. My phone is S-OFF which I read means that it does not do signature checks... however, I'm not sure if that also means it bypasses MD5 checksums - I suspect not since I'm pretty sure I saw it verifying MD5 previously. So, since I tampered with the ZIP it still may not work.
My real question now that remains is even if it will work, do I want to flash a ROM built for the ville to my villeplus. The more I read about custom ROMs the more it appears that they are extremely specific to models.
I am still extremely curious to try it... rumor has it that curiosity didn't work out so well for the cat though. :-/
Click to expand...
Click to collapse
Unfortunately, i have to fully disappoint you.
The villeplus is having the exact same hardware as the ville. Theoretically ideal. Unfortunately, HTC decided to make it a "/data/media" device unlike its brother, the ville.
Explained: the Ville has a partition for the SDCard and its mounted with its own mountpoint, /sdcard.
The Villeplus has a partition for the SDCard too, but its mounted inside the /Data partition as /data/media. This means a lot of problems from every imaginable aspect.
I spend a week together with Torxx from ViperOneS to get Viper to run on it and we found out that a.) the Kernel needs to be adjusted and b.) some libs and etc. which is real dev work and which no dev in the OneS section has time for.
Later i spent another two weeks with Philz and mdmower trying to at least get recovery to mount the sh.it thing as USB, which turned out to be impossible at this time as it is only possible through the MTP protocoll, which no recovery supports as of yet.
Since i am a n00b myself i did not entirely understand the nature of the problem, but it seems to be very complex.
At some point i suggested to actually rewrite the partitions on the phones so they would work the same way as on the ville. I even tried myself and flashed a Ville RUU to my Villeplus (it works, doesnt break anything) but with the same effect as custom roms: my SD was then in Data/media and the internal apps memory and RAM were shifted to somewhere else with not enough space so the phone kept running out of space and crashed often. Also all system components trying to access stuff on the SD failed to find their stuff and crashed.
Since we don't actually have means to change the chip controller programming so it offers the partitions differently to the ROM we cannot go that way either (Zarboz tried to explain it to me but i failed understanding it, somehow the device pathes are put into the actual chip and not part of any RUU, so to change them one would need to have some special software tool like we could have done on the HD2 back then).
The only viable way would be to adjust ROM modules and Kernel to this structure, which won't happen as no dev has this device and there are like maybe 5 active users here.
You are out of luck my friend. Sorry. I too was full of hope and gave it up when all devs i contacted signalled that there is no benefit for them and they wouldn't waste their time basically.
Sneakyghost said:
Unfortunately, i have to fully disappoint you.
The villeplus is having the exact same hardware as the ville. Theoretically ideal. Unfortunately, HTC decided to make it a "/data/media" device unlike its brother, the ville.
Explained: the Ville has a partition for the SDCard and its mounted with its own mountpoint, /sdcard.
The Villeplus has a partition for the SDCard too, but its mounted inside the /Data partition as /data/media. This means a lot of problems from every imaginable aspect.
I spend a week together with Torxx from ViperOneS to get Viper to run on it and we found out that a.) the Kernel needs to be adjusted and b.) some libs and etc. which is real dev work and which no dev in the OneS section has time for.
Later i spent another two weeks with Philz and mdmower trying to at least get recovery to mount the sh.it thing as USB, which turned out to be impossible at this time as it is only possible through the MTP protocoll, which no recovery supports as of yet.
Since i am a n00b myself i did not entirely understand the nature of the problem, but it seems to be very complex.
At some point i suggested to actually rewrite the partitions on the phones so they would work the same way as on the ville. I even tried myself and flashed a Ville RUU to my Villeplus (it works, doesnt break anything) but with the same effect as custom roms: my SD was then in Data/media and the internal apps memory and RAM were shifted to somewhere else with not enough space so the phone kept running out of space and crashed often. Also all system components trying to access stuff on the SD failed to find their stuff and crashed.
Since we don't actually have means to change the chip controller programming so it offers the partitions differently to the ROM we cannot go that way either (Zarboz tried to explain it to me but i failed understanding it, somehow the device pathes are put into the actual chip and not part of any RUU, so to change them one would need to have some special software tool like we could have done on the HD2 back then).
The only viable way would be to adjust ROM modules and Kernel to this structure, which won't happen as no dev has this device and there are like maybe 5 active users here.
You are out of luck my friend. Sorry. I too was full of hope and gave it up when all devs i contacted signalled that there is no benefit for them and they wouldn't waste their time basically.
Click to expand...
Click to collapse
Wow, Sneakyghost, I can't thank you enough for your prompt (I just PM'd him last night folks) and very thorough response.
I'm wondering why HTC did this - thinking maybe to prevent/protect users from tampering with the device - perhaps other ROMs wouldn't run on it in a stable fashion.. or they just don't want people messing with custom ROMs. Perhaps this was a new architecture for them (wondering if the One and One X followed this same design?).
In any case, looks like I'll be sticking to looking at launchers and custom widgets. I'm actually quite happy with 4.1.1 and Sense (maybe because I'm new to Android, not sure), I mainly wanted to try experiment with custom ROMs, and learn about how all this stuff works. At least till the M4 comes out anyways..
Thanks again so much for your response, it is much appreciated and well explained.
Sneakyghost said:
... Unfortunately, HTC decided to make it a "/data/media" device unlike its brother, the ville.
Click to expand...
Click to collapse
Oh the irony, the (unreleased) 4.2 update for ville actually reformats partitions for data media. I don't think the update will ever be officially available to US users, but it is funny nonetheless.
This, my friend, is indeed ironic, if not even sad.
Considering what it means, I come to understand that porting ROM's from Ville to Villeplus would have gotten much easier then. Only that it is too late.
Torxx and I gave up due to the amount of work attached to the previous system structures, but if the Ville turns into a datamedia device with that update, many ROM devs and chefs would have to deal with it plus HTC would have done the most difficult part already anyway...
What a shame that this comes so late now and doesn't even get released probably...
mobile post
Q&A for [ROM][2.3.6] AEON v1.4SL STABILITY AT ITS FINEST
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][2.3.6] AEON v1.4SL STABILITY AT ITS FINEST. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Where to go from here
Not sure what happened, hope this didn't get posted twice.
Hi,
I am still happily using the Samsung Infuse 4G, and was running the stock GB 2.3.6. No real issues, and although starting to get a sense of it being dated was having no issues and in no rush to go out and upgrade. However, we recently purchased a 2015 Subaru Legacy with their Starlink multimedia system. The Infuse, as it was with the stock GB had no problems connecting via BT for phone and audio functionality. But, the car system reports that the phone is not compatible for messaging. In my endeavors to understand why, I thought, maybe incorrectly, that GB does not support the MAP profile.
So, that led me to, is it possible to add that, and how do you do it, or is it time to upgrade? Flash a new ROM? I can't seem to find much on the specific issue I am trying to resolve and if a new ROM would fix it, but since the phone is way out of warranty I decided to try rooting and flashing a ROM. I am new to this so I went with the Aeon 1.4 ROM based on GB 2.3.6 (I think), hoping that it was a bit less risky. Everything went well and seems to be working fine. But, it did not fix the messaging issue with the car. I assume because it is really still GB.
Am I going about this wrong? Would a flash up to ICS or beyond possibly do it? I am not totally against a new phone, but till now I wasn't even thinking about a new phone. Suggestions? Which ICS, or other ROM would you recommend? Thanks all.
Hi there,
mainwheel said:
Would a flash up to ICS or beyond possibly do it? I am not totally against a new phone, but till now I wasn't even thinking about a new phone. Suggestions? Which ICS, or other ROM would you recommend? Thanks all.
Click to expand...
Click to collapse
I think your car requires the newest bluetooth protocol (4.0), something that is primarily hardware based.
I could be (and hopefully am) wrong here, but the only way to find out is to do a ROM walkabout.
ICS is out right off the bat, as bluetooth was borked in that version (IIRC). You'll need to upgrade to that in the process anyway, as CWM for this device doesn't like drastic changes.
I am biased, but I would try CarbonROM 4.4.4 (the latest, unofficial build) or at the very least CM 10.1. The former would have the best chance of support (being latest firmware available), but it may be overkill for your situation (newer versions = harder on battery life).
So I would try CM 10.1 after stepping up to ICS (having done a full nandroid before all this), and if the car still refuses to connect, try Carbon. Then you may be able to prove me wrong.
Hope this helps.
Sent from my MeMO Pad 8"
joel.maxuel said:
Hi there,
I think your car requires the newest bluetooth protocol (4.0), something that is primarily hardware based.
I could be (and hopefully am) wrong here, but the only way to find out is to do a ROM walkabout.
ICS is out right off the bat, as bluetooth was borked in that version (IIRC). You'll need to upgrade to that in the process anyway, as CWM for this device doesn't like drastic changes.
I am biased, but I would try CarbonROM 4.4.4 (the latest, unofficial build) or at the very least CM 10.1. The former would have the best chance of support (being latest firmware available), but it may be overkill for your situation (newer versions = harder on battery life).
So I would try CM 10.1 after stepping up to ICS (having done a full nandroid before all this), and if the car still refuses to connect, try Carbon. Then you may be able to prove me wrong.
Hope this helps.
Sent from my MeMO Pad 8"
Click to expand...
Click to collapse
Thanks very much for your reply.
Being a hardware issue is something I have considered, but not knowing enough to understand why it might work virtually flawlessly for phone and audio streaming in the car, I was hopeful the hardware would support additional Bluetooth profiles, that are added with a new ROM. But then again, I would not be surprised to do the walkabout and end up at the store for a new phone in the end anyway.
I will be looking for an ICS ROM, but it sounds like it doesn't matter which one I use because I won't be staying there?
I have done, and will do again, backups, but I am little unclear on a few things. CWM is on the phone, but I actually used ROM Manager for the flashing I've done. Are they the same thing? It uses CWM. Also, I've seen various references to making sure the phones identity (not sure that's the right term) is saved, and I take that to mean that after flashing the phone may no longer be able to access phone carrier service. Is that a real possibility? And, is it necessary to remove the SD card? Thanks again.
mainwheel said:
Thanks very much for your reply.
Being a hardware issue is something I have considered, but not knowing enough to understand why it might work virtually flawlessly for phone and audio streaming in the car, I was hopeful the hardware would support additional Bluetooth profiles, that are added with a new ROM. But then again, I would not be surprised to do the walkabout and end up at the store for a new phone in the end anyway.
I will be looking for an ICS ROM, but it sounds like it doesn't matter which one I use because I won't be staying there?
I have done, and will do again, backups, but I am little unclear on a few things. CWM is on the phone, but I actually used ROM Manager for the flashing I've done. Are they the same thing? It uses CWM. Also, I've seen various references to making sure the phones identity (not sure that's the right term) is saved, and I take that to mean that after flashing the phone may no longer be able to access phone carrier service. Is that a real possibility? And, is it necessary to remove the SD card? Thanks again.
Click to expand...
Click to collapse
I would recommend Entropy's ICS build, which I have a mirror of, accessed from my signature link.
ROM manager loads CWM (same author, ROM manager is IIRC just the Play Store delivery mechanism for CWM), so once you have CWM, you are good to go for your walkabout.
Yes, you want to make sure to back up your IMEI information first, because that stuff can get lost, which if lost, will deny you access to your carrier. There is a way to retrieve it if lost on this device, but an ounce of prevention is worth a pound of cure. Check the CM10.x thread on instructions how to flash (with links to the IMEI backup).
No need to remove the SD card, but if you don't need it for a flash, I would remove it anyway (or back up it's contents to your PC first - in case in the unlikely event - I'm paranoid about those things - CWM goes a little liberal with the factory reset).
Hope this helps.
joel.maxuel said:
I would recommend Entropy's ICS build, which I have a mirror of, accessed from my signature link.
ROM manager loads CWM (same author, ROM manager is IIRC just the Play Store delivery mechanism for CWM), so once you have CWM, you are good to go for your walkabout.
Yes, you want to make sure to back up your IMEI information first, because that stuff can get lost, which if lost, will deny you access to your carrier. There is a way to retrieve it if lost on this device, but an ounce of prevention is worth a pound of cure. Check the CM10.x thread on instructions how to flash (with links to the IMEI backup).
No need to remove the SD card, but if you don't need it for a flash, I would remove it anyway (or back up it's contents to your PC first - in case in the unlikely event - I'm paranoid about those things - CWM goes a little liberal with the factory reset).
Hope this helps.
Click to expand...
Click to collapse
Thanks Joel. I have now installed Entropy. Don't know whether everything else is working, but I do know that I can not connect to my wifi. Keep getting "authentication problem." I see that it is a known problem, but I'm not finding a solution. Not quite ready to go the next step (time constraint), so I'm hoping there is a fix, or at least a workaround. Kind of a bummer not having access to wifi. Any suggestions?
mainwheel said:
Thanks Joel. I have now installed Entropy. Don't know whether everything else is working, but I do know that I can not connect to my wifi. Keep getting "authentication problem." I see that it is a known problem, but I'm not finding a solution. Not quite ready to go the next step (time constraint), so I'm hoping there is a fix, or at least a workaround. Kind of a bummer not having access to wifi. Any suggestions?
Click to expand...
Click to collapse
I wouldn't worry about it. Entropy is just a step-through (because BlueTooth is broken as well) and there are other ways to get the other ROMs onto the device (if they are not there already) such as adb push or MicroSD + Built-in Filemanager App. Higher versions will have that fixed anyway.
Downloadable CM 10.1
joel.maxuel said:
I wouldn't worry about it. Entropy is just a step-through (because BlueTooth is broken as well) and there are other ways to get the other ROMs onto the device (if they are not there already) such as adb push or MicroSD + Built-in Filemanager App. Higher versions will have that fixed anyway.
Click to expand...
Click to collapse
Thanks again Joel.
I don't have a lot on my data plan, so I rely on wifi quite a bit. But for now, not a big deal and will try to upgrade asap. No issues with getting the file to the phone, but I am having some difficulty finding a downloadable CM 10.1 (actually it is 10.2), and a gapps file for it. The XDA forum I went to doesn't work and if I go to the mirror site it tells me the file is too big or something and I'm not able to download. Haven't scoured the internet looking for it, thought I might save some time if you know where I can get it. If not, I'm thinking just try the Carbon ROM, assuming I can find it. I know you recommend CM first. George
mainwheel said:
Thanks again Joel.
I don't have a lot on my data plan, so I rely on wifi quite a bit. But for now, not a big deal and will try to upgrade asap. No issues with getting the file to the phone, but I am having some difficulty finding a downloadable CM 10.1 (actually it is 10.2), and a gapps file for it. The XDA forum I went to doesn't work and if I go to the mirror site it tells me the file is too big or something and I'm not able to download. Haven't scoured the internet looking for it, thought I might save some time if you know where I can get it. If not, I'm thinking just try the Carbon ROM, assuming I can find it. I know you recommend CM first. George
Click to expand...
Click to collapse
Hi George,
My signature link contains the CM10.1 ROM (and Gapps) as well. I had problems with CM10.2 back in the day (wouldn't install), so I would recommend 10.1 over 10.2.
My Dropbox may be exhausted for the day (sometimes it gets like that) but I may have a copy on well, Copy, that I could send if necessary. Just let me know if you have problems downloading from my mirror first.
joel.maxuel said:
Hi George,
My signature link contains the CM10.1 ROM (and Gapps) as well. I had problems with CM10.2 back in the day (wouldn't install), so I would recommend 10.1 over 10.2.
My Dropbox may be exhausted for the day (sometimes it gets like that) but I may have a copy on well, Copy, that I could send if necessary. Just let me know if you have problems downloading from my mirror first.
Click to expand...
Click to collapse
Joel,
Maybe I'm just missing something. Not having a problem downloading, I'm having a problem finding the files to download.
The only link I find (it's the link that says something about development files?) takes me to the XDA CM 10.2 forum where I wasn't able to get it. Maybe I'm just missing it in your signature links. I see references to Carbon and other stuff. George
mainwheel said:
Joel,
Maybe I'm just missing something. Not having a problem downloading, I'm having a problem finding the files to download.
The only link I find (it's the link that says something about development files?) takes me to the XDA CM 10.2 forum where I wasn't able to get it. Maybe I'm just missing it in your signature links. I see references to Carbon and other stuff. George
Click to expand...
Click to collapse
George,
Each list item has two links....the original source item (thread), and then the dropbox download link (labelled "download") so you are looking for this.
Hope this helps.
joel.maxuel said:
George,
Each list item has two links....the original source item (thread), and then the dropbox download link (labelled "download") so you are looking for this.
Hope this helps.
Click to expand...
Click to collapse
DOH! Didn't even see that there were two links. Sorry about that. Think I've got everything now, and can find it again if I need it. Now to do the work. Thanks for your help. Will let you know how it goes. George
mainwheel said:
DOH! Didn't even see that there were two links. Sorry about that. Think I've got everything now, and can find it again if I need it. Now to do the work. Thanks for your help. Will let you know how it goes. George
Click to expand...
Click to collapse
Hi Joel,
Got it upgraded to CM 10.1. All seems well. Unfortunately, it did not fix the compatibility problem with messaging and our car, as you correctly suggested might happen. Is there anything about Carbon that gives you reason to think it might work? As I said in the original post, I made some assumptions about the problem (Bluetooth MAP profile based on some reading), and that might be a software fix. But, of course, I may be completely wrong about it. Thanks. George
mainwheel said:
Hi Joel,
Got it upgraded to CM 10.1. All seems well. Unfortunately, it did not fix the compatibility problem with messaging and our car, as you correctly suggested might happen. Is there anything about Carbon that gives you reason to think it might work? As I said in the original post, I made some assumptions about the problem (Bluetooth MAP profile based on some reading), and that might be a software fix. But, of course, I may be completely wrong about it. Thanks. George
Click to expand...
Click to collapse
Hello again George,
Nothing about Carbon in general, but KitKat, yes...
Android 4.4 support for two new Bluetooth profiles to let apps support a broader range of low-power and media interactions. Bluetooth HID over GATT (HOGP) gives apps a low-latency link with low-power peripheral devices such as mice, joysticks, and keyboards. Bluetooth MAP lets your apps exchange messages with a nearby device, for example an automotive terminal for handsfree use or another mobile device. As an extension to Bluetooth AVRCP 1.3, users can now set absolute volume on the system from their Bluetooth devices.
Click to expand...
Click to collapse
Gone this far, might as well give it a shot. :fingers-crossed:
joel.maxuel said:
Hello again George,
Nothing about Carbon in general, but KitKat, yes...
Gone this far, might as well give it a shot. :fingers-crossed:
Click to expand...
Click to collapse
I guess it couldn't stay easy. My attempt to install CARBON (two different download versions) failed, I am getting an error I don't understand.
First, when I go to wipe dalvik I get E: unknown volume for .... (/sd-ext) I can not read it very well because of the background image. Where I put the ... it looks like path.
Then
This ROM uses an imcompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
Then
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/CARBON-KK-NIGHTLY-20141102-0915-infuse4g.zip
(Status 7)
Installation aborted.
Any ideas what this means? I can reload CM 10.1, so I am not bricked or anything. I appreciate your help.
I did try to get some help from the IRC forum at CARBON, but haven't gotten any replies.
George
mainwheel said:
I guess it couldn't stay easy. My attempt to install CARBON (two different download versions) failed, I am getting an error I don't understand.
First, when I go to wipe dalvik I get E: unknown volume for .... (/sd-ext) I can not read it very well because of the background image. Where I put the ... it looks like path.
Then
This ROM uses an imcompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
Then
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/CARBON-KK-NIGHTLY-20141102-0915-infuse4g.zip
(Status 7)
Installation aborted.
Any ideas what this means? I can reload CM 10.1, so I am not bricked or anything. I appreciate your help.
I did try to get some help from the IRC forum at CARBON, but haven't gotten any replies.
George
Click to expand...
Click to collapse
There's this tutorial (section 27), but what may be happening is a drastic change in ROM's for CWM (which falls under what status 7 error scope - along with corrupted IMEI, etc).
My upgrade path long ago (coincidentally) was Stock -> CM9 -> CM10.1 -> Beanstalk 4.4.2 -> CarbonROM 4.4.4.
You can, however cheat, by disabling voodoo lagfix in CWM settings. Otherwise, you may need to find the oldest CarbonROM Kitkat you can grab (4.4.2), to make that last (small) jump to 4.4.4.
If still doesn't work, roll back to CM10.1, make sure everything is order (including calling), and try again.
joel.maxuel said:
There's this tutorial (section 27), but what may be happening is a drastic change in ROM's for CWM (which falls under what status 7 error scope - along with corrupted IMEI, etc).
My upgrade path long ago (coincidentally) was Stock -> CM9 -> CM10.1 -> Beanstalk 4.4.2 -> CarbonROM 4.4.4.
You can, however cheat, by disabling voodoo lagfix in CWM settings. Otherwise, you may need to find the oldest CarbonROM Kitkat you can grab (4.4.2), to make that last (small) jump to 4.4.4.
If still doesn't work, roll back to CM10.1, make sure everything is order (including calling), and try again.
Click to expand...
Click to collapse
Thanks again Joel.
I may have to bag this whole project. Must be a little late doing this. Too much time and trouble searching for files that can't be downloaded. I could not find an early CarbonROM KitKat to download. I could not find a BeanStalk to download. I find links that point to a defunct website. I did finally find a CM11 which I did download, but I did not see a gapps file to go with it, unless I can use any 4.4 gapps. Also, when I run CWM there is no reference to lagfix. I appreciate all the help, but I don't want to take any more of your time. George
mainwheel said:
Thanks again Joel.
I may have to bag this whole project. Must be a little late doing this. Too much time and trouble searching for files that can't be downloaded. I could not find an early CarbonROM KitKat to download. I could not find a BeanStalk to download. I find links that point to a defunct website. I did finally find a CM11 which I did download, but I did not see a gapps file to go with it, unless I can use any 4.4 gapps. Also, when I run CWM there is no reference to lagfix. I appreciate all the help, but I don't want to take any more of your time. George
Click to expand...
Click to collapse
Hi George,
Any 4.4.2 Gapps will work. I am uploading one right now (along with older Beanstalk and CM11)...
https://www.dropbox.com/sh/smohomrdx0oqn76/AACfrsgXTEHhDmVtwEWj6EA5a?dl=0
...it may take an hour for files to appear, so keep posted, if still interested.
Also, another way to disable voodoo lagfix (if not found in CWM) is to create a folder on internal storage called Voodoo, and then a folder inside that called disable-lagfix.
Hope this helps.
joel.maxuel said:
Hi George,
Any 4.4.2 Gapps will work. I am uploading one right now (along with older Beanstalk and CM11)...
https://www.dropbox.com/sh/smohomrdx0oqn76/AACfrsgXTEHhDmVtwEWj6EA5a?dl=0
...it may take an hour for files to appear, so keep posted, if still interested.
Also, another way to disable voodoo lagfix (if not found in CWM) is to create a folder on internal storage called Voodoo, and then a folder inside that called disable-lagfix.
Hope this helps.
Click to expand...
Click to collapse
Thanks Joel. I appreciate the help and will try to make some time to install these files. Will let you know. George
joel.maxuel said:
Hi George,
Any 4.4.2 Gapps will work. I am uploading one right now (along with older Beanstalk and CM11)...
https://www.dropbox.com/sh/smohomrdx0oqn76/AACfrsgXTEHhDmVtwEWj6EA5a?dl=0
...it may take an hour for files to appear, so keep posted, if still interested.
Also, another way to disable voodoo lagfix (if not found in CWM) is to create a folder on internal storage called Voodoo, and then a folder inside that called disable-lagfix.
Hope this helps.
Click to expand...
Click to collapse
Hi Joel,
Unfortunately, none of these 4.4.x versions will install, same error. And placing Voodoo/lagfix/ folder doesn't seem to work either, same error. If the problem is the jump to the next version is too great, maybe an earlier version of something, 4.2 or earlier? George