Related
Nookie Froyo 0.6.8
is a development build of Froyo 2.2.1 for the Nook Color.
ClockworkMod flashable! - info below, please *read carefully* before flashing!
This build is near-AOSP and contains almost no extra software not deemed required for the device to function normally.
It is pre-rooted with SuperUser, busybox, SoftKeys v3.07, and ROM Manager 3.0.0.5 however.
The eventual intention will be a build that other devs and users can easily fork and create their own custom builds, themes, roms, etc.
** THIS IS A DEVELOPMENT BUILD **
Use this at your own risk! Myself, XDA, and NookDevs are *NOT RESPONSIBLE* for anything that happens directly or indirectly related to this software!
We're approaching a daily driver! Most things work now, including mp3 and video playback. Post any bugs you find here!
I'd like to thank all the nook color devs involved in getting to this state, testing, documenting, etc. We've got an amazing group of minds behind this device!
INFO
The microSD card image contains 4 partitions:
/dev/block/mmcblk1p1 : boot (fat32)
/dev/block/mmcblk1p2 : system (ext2)
/dev/block/mmcblk1p3 : data (ext3)
/dev/block/mmcblk1p4 : sdcard (fat32)
Use these partition IDs when following guides that require mounting/remounting filesystems.
What's Working:
MP3 playback
Video playback
Youtube, Pandora and other mp4 streaming apps (apps not included)
Accelerometer!
Wifi (adhoc + infrastructure!)
Graphics acceleration (LWP!)
Sound
Browser
Mostly working
Lockscreen is wrong size - REBOOT to fix
Not included / Not working
gapps ( gmail, youtube, maps, etc ) - can be installed, youtube fixed!
Bluetooth
FM radio
This build was created using the B&N kernel sources for 1.0.0, Omappedia's Froyo source ( currently RLS27.9.0.RC0 ), and binary drivers from TI for wireless, SGX530 acceleration, and DSP codecs.
Download:
This SD image requires a 2GB microSD card! Bigger is OK, smaller is not ok!
Note: if you wish to use a larger microSD card, you can use a partition editor to increase the size of the /sdcard partition (partition 4, fat32) *after* writing the image to your card.
Simply unzip this image and dd the file to your (empty) SD card, just like nooter.
nookie-froyo-SDIMAGE_2GB-0.5.1.gz 76459ec18fd32885257a3c8b7dbb2b76
nookie-froyo-SDIMAGE_2GB-0.5.6.img.gz 74e5310bcc21edf326bdc73a5652c124
nookie-froyo-SDIMAGE_2GB-0.5.8.img.gz 15158e735517c209a8f2ed14683a589c
nookie-froyo-SDIMAGE_2GB-0.5.9.img.gz 7d30f56eeede98ee1e99a0766f69dea3
nookie-froyo-SDIMAGE_2GB-0.6.6.img.gz fc58aa06fcfe1f46939ab72e38292abe
nookie-froyo-SDIMAGE_2GB-0.6.7.img.gz 92ef91dbac7a7baad3999256597b7920
nookie-froyo-SDIMAGE_2GB-0.6.8.img.gz
MD5: 18e7cc8393681ec590f698b7a671e859
If you want to customize your SD card, upgrade an already burned Nookie Froyo SD, live on the edge and burn it into your eMMC, or just want to poke around, download the base filesystem:
nookie-froyo-base-0.5.1.tar.gz 3e95a33e3926bc88011e66a724dccf8f
nookie-froyo-base-0.5.6.tar.gz 4419b21dd8eb56f6a6537345aa1c8ba1
nookie-froyo-base-0.5.8.tar.gz 2c279dbdaa6aad480590d55e48abf8ca
nookie-froyo-base-0.5.9.tar.gz 093a964685f0cbea2ef1aa8f6f0d7581
nookie-froyo-base-0.6.6.tar.gz 2304e337c351c667f27eb9aa4c3791b8
nookie-froyo-base-0.6.7.tar.gz 99b6a9d991951c368cf1f6b3429be958
nookie-froyo-base-0.6.8.tar.gz
MD5 c3c7aea7cdf8a3dde32acc1694f633aa
This archive also contains an uncompressed ramdisk image which you can easily edit, package, and copy to your boot partition.
ClockworkMod Flashable ZIP!
*IMPORTANT*
- please wipe data/factory reset if you're coming from B&N stock firmware or another rom!!
- please see other threads about installing and using CWM recovery - keep this thread to NF issues please
- this has been tested only using CWM 3.0.0.5 downloaded from market, be warned it may not work with IOMonster's kit or other versions. Let us know if you try and it does!
- replaces kernel and ramdisk - if you were using an alternate kernel you'll need to reflash it.
- This will irrevocably erase and replace the software on your eMMC! MAKE BACKUPS BEFORE FLASHING, you have been warned.
If you're upgrading from an older version of Nookie Froyo, you should not have to wipe - however if you do have problems *wipe data* and try again.
*IMPORTANT* - this zip does not require any extra steps such as formatting /boot, changing system permissions, and does not replace or remove CWM. If you are coming from a ROM that required these extra steps and are having issues, *please post your questions there* so the dev can be prompted to correct those issues properly.
If you're coming from a rom that doesn't support CWM properly see the following thread:
http://forum.xda-developers.com/showthread.php?p=11437545
Installing /system will take some time, and the progress bar doesn't update in realtime; you haven't 'locked up', just be patient as it may take a few minutes.
nookie-froyo-flashable-0.6.6.zip 6f61a464483ecf45d6e6e2d199b44d6c
nookie-froyo-flashable-0.6.7.zip 9bd13877addbad725a5bfe1eb13412df
nookie-froyo-flashable-0.6.8.zip
MD5: 03544d6a5a52eebdb468c89a5a2581e9
Please do not PM me for help, that's what this forum and the IRC rooms are for - I simply do not have the time to answer all of your questions, and asking them in a public forum will allow others with the same issue to help or learn from your experience!
CHANGELOG
v 0.5.6
permissions corrected on /system/bin/input for SoftKeys
corrected default cpu governor to conservative
added SuperUser
added busybox 1.17.2
added SoftKeys 3.00 ( thanks bpk! )
AdHoc WIFI support enabled
crypto/cryptofs added in kernel for ASEC support (required for installing some apks such as Angry Birds)
v 0.5.8
uses the /cache partition on eMMC instead of combining with data
replaces u-boot.bin to remove the 'touch the future..' splash (trademark)
increased refresh rate to improve responsiveness and reduce flicker (see tips in the next post)
added sensors lib - accelerometer works!
v 0.5.9
default web browser FC fix - no longer dies on location requests!
v 0.6.6
Youtube, Pandora, and other streaming media should now work.
added codecs for more media formats - including hw accelerated mp3 and video
vold reverted - no more broken SD card message
flashable zip!
updated SoftKeys to 3.07
fixed a /cache issue which sometimes prevented market downloads
v 0.6.7
SD card mount fixed - please post if you continue to have issues
Added back Mms, Phone, Camera, Telephony apks to resolve missing apps in Market - more apps should be available
Modified CWM zip reliability
v 0.6.8
Corrected improper handling of Format SD Card option - no longer formats /boot!
Touchscreen enhancements - no need to toggle screen on boot and better responsiveness around the edges - thanks deeper-blue!
Please see the updated issues/workarounds list in the following post
For more information, sources, and install instructions, please see:
http://nookdevs.com/NookColor:_Nookie_Froyo
Need help? Want to contribute? Join us in IRC! irc.freenode.net
#nookcolor - general chat, questions, ask for help here
#nookie - development
Do not try to Format SD card from Settings -> SD & Phone storage!
- there is currently a bug that causes the system to format the /boot partition instead of /sdcard when this option is used, leaving your NC unbootable. Format your SD card in your PC or another device if you need to! - fixed in 0.6.8!
FIRST BOOT TIPS -
On first boot, Launcher and SoftKeys will fight for control of the home intent - that is, when you boot the first time, your NC will ask you to pick your home activity.
*CHOOSE LAUNCHER* at first (DO NOT select 'always use this action'), and let the system boot and stabilize (3-4 minutes).
Hit Home (the N button). You'll be asked to choose your activity again, this time choose SoftKeys.
Try using one of the SU-required buttons (back or menu), and after a few moments SuperUser will prompt you to accept the action.
SoftKeys 3.06+ now prompt for SU permission at startup, just accept the superuser prompt when it pops, you'll still want to let the system stabilize for a minute or two.
If SoftKeys fails to ask for SU permissions, "Unable to execute as root":
Go to Settings -> Applications -> Manage Applications -> 'All'
Select SoftKeys from the list
'Force close' Softkeys if it's running, then 'Clear defaults'
Hit the N button, choose SoftKeys when prompted to choose your home action, accept the SU prompt when it pops.
Workarounds for some known bugs/issues:
(default in 0.5.8+) Improved Refresh-rate (no flicker! thanks [mbm]!): this should set the refresh rate to 68hz, the supposed default for the Nook Color's LCD panel -
Code:
adb shell echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings
Browser: force closes when opening a website that tries to use location services, due to the missing GPS. Try browsing to a url by typing in the google search box, and if you can get into the browser menu changing your homepage away from google will stop it from FC'ing on open.
Lockscreen wrong size: Simply reboot to correct this.
Touchscreen is slow/unresponsive:
Turn your screen off and then back on.
Disable Haptic Feedback in Settings -> Sounds.
Also, see this page for a possible calibration fix: http://nookdevs.com/Recalibrate_the_NookColor_touch_screen
(fixed in 0.5.6 w/included SoftKeys 3.00) No buttons! Try: http://forum.xda-developers.com/showthread.php?t=860153
(fixed in 0.5.6) SoftKeys - in 0.5.1 softkeys' buttons do not work due to a permissions issue. To fix, do:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
adb shell chmod 0755 /system/bin/input
Please post issues/workarounds/bugs in this thread, I'll try to keep this list updated.
To answer from the other thread...
Timeframe-- well, this isn't me doing this. But I think the devs just want to take the edges off, so be patient... I'm just the messenger on the news that it's been done. This is other people's accomplishment.
In fact, froyo was done weeks ago, though not entirely from open-source/freely distributed components like this (as far as I know).
To answer some questions--
BT not working, FM not working, accellerometer not working. Softkeys should work... dont' see why not anyway. It's stock froyo. No gapps, no Superuser.apk, no nothing over and above AOSP. Overclocking not in but should be possible... video playback hasn't been tried (it's early still!).... battery life who knows I haven't even had a chance to let it run down... I posted because the news was "out" anyway. I also can't compare to stock because I've never run stock, believe it or not. But it's based on the same kernel 2.6.29. It boots off a SD partitioned for system, data, cache, and sdcard. Only thing (I think) it touches on the internal storage is resetting that boot counter, otherwise you'd only get 7 boots at a time. Doesn't need much space. 2GB should be enough. That's what phones have anyway. Guess it depends what you want to do with it. Performance is decent, not steller compared to my g2 at least. Will benefit from OC.
devis said:
@fattire
Questions on everyone's (well, mine at least) mind... please answer as much as you can, and a big big thank you!!!
1. Is BT working?
2. Is FM working?
3. Can we still use SoftKeys for hardware key emulation?
4. Can we overclock the processor?
5. How's the video playback?
6. How's the battery life compared to stock?
7. Since you're booting from SD, does that mean the internal memory of the NC remains untouched, should we need to boot stock?
and
8. How does the device feel overall?
Click to expand...
Click to collapse
Nice stuff guys keep up the stellar work
Sent from my LogicPD Zoom2 using XDA App
So awesome, looking forward to the progression of this!
I got my SD to boot tonight!
It defiantly isn't for the faint of heart but it seems to work well enough as a good base to start on. Pretty snappy to boot.
I would like to emphasize that this is VERY rough around the edges and if you aren't planning on hacking with the kernel, or code, or attempting to make your own rom then this is NOT for you.
http://i.imgur.com/WRyNV.jpg
http://i.imgur.com/H4ahM.jpg
Defiantly awesome work (and pure AOSP + TI drivers) which means no propritary B&N bits
Thanks for releasing such and early build to the public. It's not often you see that.
(I won't even consider playing with this build)
As a humble Analysts I grovel at the feet of your magnificent tech prowess.
(thanks)
Does this include a working JIT or is that one of the things in progress?
That seems to be one of the more compelling things from froyo (at least for a device with more internal storage than a nexus one). I would expect (well, hope anyway) that the froyo JIT would have a noticeable impact on the speed...
Mods, can we please stickie this?
Very awesome... Will try it out later today!
Since this runs off the sdcard can you power down the NC and remove the sdcard and boot normally?
Novarider said:
Since this runs off the sdcard can you power down the NC and remove the sdcard and boot normally?
Click to expand...
Click to collapse
Read: http://nookdevs.com/NookColor:_Nookie_Froyo#After_you_have_burned_the_uSD_card
To get back to stock, just remove the uSD card and reboot.
Click to expand...
Click to collapse
It has all the info you want, and is mentioned in the first post.
cicada said:
Workarounds for some known bugs:
No buttons! Try: http://forum.xda-developers.com/showthread.php?t=860153
Click to expand...
Click to collapse
You also have the option of converting the volume buttons to back/menu as well. It is documented in this thread, but the filenames have changed in this build. You will need to modify the following files..
/system/usr/keylayout/qwerty.kl
/system/usr/keylayout/twl4030-keypad.kl
I am not a developer.
I am not likely to become one at this stage of the game...
I am, however, either brave or stupid because I am downloading the image and will see if it will boot on my NC.
I do this because:
A) I want to SEE froyo running on my NC, and
2) If I have any problems, feedback might help the devs
I love seeing all the progress that has been made on these things.
Is flash supported in the browser with this initial froyo build?
jay084 said:
Is flash supported in the browser with this initial froyo build?
Click to expand...
Click to collapse
I tested flash and it does work.. The flash plugin is not included in the build however, I had to find it and install it via ADB.
Just rebooted back to my regular rooted NC system after pulling the sdcard and can only say-
Marvelous.
Yes, it is slow, no keyboard and all of the other things that were spoken of in the initial posts, but IT WORKS.
I don't have time to do much else with it right at the moment, but I will mess with it more later.
BertoJG said:
I tested flash and it does work.. The flash plugin is not included in the build however, I had to find it and install it via ADB.
Click to expand...
Click to collapse
Could you post the flash plugin you used? I would really appreciate it. Could you also comment on the quality of flash videos online. I'd like to watch espn3 on the nook...in bed...lol
OK, so I booted the rom, and followed the instructions at nookdevs...
Installing superuser.apk and pushing su seemed to work just fine!!!
Softkeys installed and got superuser permissions and works as well.
Installed astro file manager, and that works fine too...
At that point, I wanted to mount the usb storage and move over a bunch of APK files... mounted the nook and could only see the mlo, img file etc... no problem creating an apk folder and putting files in there, but then I can't see that folder when I look for it in astro....
Any info on simply copying files via USB using this build?
Also, thanks to all the devs for the awesome work... looking forward to playing around with this more!!!
Let's start.
System: Android 2.3.3 (Gingerbread)
DSC ROM is based on Olleh 407/406 beta ROM.
Our team point is to provide best ROM for Streak, stable and fast enough for everyday use.
(and making waiting offical Dell release a bit less stressful )
DSC name was an acronym for Dell Streak Club, but now i'd say it's Dell Streak Community ROM, due to all efforts of everyone, involved in the project (v1.0 download count from my server is over 100.000 now). Thank you guys!
Take a look at Quick Solutions section. It may have an answer for your problem.
Announcement
v2.0 Release information.
Latest update information.
Using 366 BB (AMSS) without blinking leds issue. (Just for information, superseded with 1.2 update)
List of currently supported languages.
Knowing your way around here.
DSC Team Phoenix Universal kernel
Arabic patch:
http://n0p.8bit.fm/streak/v2.0-Arabic.zip
With PDroid:
http://n0p.8bit.fm/streak/v2.0-Arabic-PDroid.zip
Please carefully read all information contained in this post. It will save you a lot of time later.Introduction and changes from original 407/406 Olleh ROM:
Initially made by two members (n0p and wway) of Russian Dell Streak Club. Russian users are advised to start from here.
Current team list:
n0p - it's me
wway - theming/testing.
streakOwner - lots of ideas and testing.
ltrifonov - kernel development/system builder.
greg9100(GSpecial) - kernel development/system builder.
hunderteins - USSD hack, 14 channels WiFi hack.
hPa – kernel/Wifi driver hacks.
lordmorphous - theming/testing/framework hacking.
btvbtv - testing/cable solution/support
uglyrooster - testing/WiFi solution.
khoacoi - file hosting/support.
dsteinberg - testings/ideas.
Trankvilli - testing.
attila.m - extensive testing.
_2bad4u_ - theming.
dr.nemro - Arabic patch.
Ace38 - Wonderful new boot animation for 2.0.
uluvali - testing/support.
Huge thanks to everyone who uses this ROM - for testing, support and important feedback.
Custom DSC-Team kernel. UV/OC, CIFS an TUN support, USB automount/OTG cable support.
Mugen Power batteries support - DSC Mugen Power config.
Deodexed.
Rooted with SimpleSU
Internationalized/Localized
Contains great GingerTrue theme by wway
ICS animations and QuickPanel added by wway.
Stock dialer works on non-stock DPI > 160.
One of random reboot bugs (division ny zero) nailed down.
Changed memory management and OOM grouping a bit.
CPU governor is set to "conservative" to preserve battery. CPU ramp tweaked for less lag.
Manual change instructions. Also please look here.
Stage Launcher removed. Available as additional update.
Some engeneering leftovers removed.See this.
Added theme-independent CRT animation and enabled hardware UI acceleration.
DalvikVM changed. Dalvik parameters changed.
Screen turns on after power disconnect.
Battery level on standard lockscreen.
Revised tweaks (configurable).
Rogers tethering (removed APN lock).
"Backcover removed" detection removed.
Custom bootanimation by Ace38
Patches in WiFi driver - sleep timeout and power management.
DSConfig (system) – DSC ROM configuration tool.
DSC Gain - audio driver gain / brightness control.
Vibration on poweroff/reboot configurable.
Theme-independent Reboot option.
DSC Wallpapers - Launcher-free wallpapers pack.
Third-party apps, included in ROM can be removed due to new post-install process.
WiFi driver hacked to enable 14 channels
Proximity sensor (touchpad freeze) fixes.
Phase2 auth setting fixed.
Power button dejitter patch.
USB automount.
Number of SoD drastically redused. I personally haven't experienced any in two months.
init.d support.
zipalign script added.
Volume levels altered.
Media sounds from FroYo added.
USSD requests work.
Built-in WiFi fixer.
Camera has Torch mode.
Configurable CPU undervolting.
FPS uncap patch.
BB check removed.
EXT4 driver for EXT2/3 filesystems.
Configurable wake by other keys.
Boot time significantly reduced.
Please read following before flashing!
Please delete or move all apps manually to internal memory before flashing.
Guides and flashing instructions
Painless migration from Froyo with all apps.
Known bugs:
Google Maps causes battery drain. Freeze it if you're not using it.
DSC ROM downloads:
http://n0p.8bit.fm/streak/DSCv2.0-rel.zip
DSCv2.0-rel.zip on Google Drive
PDroid patch (lightweight privacy solution, you'll need to install the control app from Play):
http://n0p.8bit.fm/streak/PDroid-v1.31-DSCv2.0.zip
PDroid-v1.31-DSCv2.0.zip on Google Drive
--
Mirror:
http://www.littlemaruko.com/Nopteam/DSCv2.0-rel.zip
PDroid:
http://www.littlemaruko.com/Nopteam/PDroid-v1.31-DSCv2.0.zip
Update (should be flashed only over 2.x.x full ROM) to 2.3:
http://n0p.8bit.fm/streak/updDSCv2.3.zip
updDSCv2.3.zip on Google Drive
Mirror:
http://www.littlemaruko.com/Nopteam/updDSCv2.3.zip
Update for PDroid users:
http://n0p.8bit.fm/streak/updDSCv2.3-pre-PDroid.zip
updDSCv2.3-PDroid.zip on Google Drive
Mirror:
http://www.littlemaruko.com/Nopteam/updDSCv2.3-PDroid.zip
You can safely flash this ROM over any GB ROM without losing your data.
For faster flashing - flash PDroid right after ROM to skip cache rebuilding twice.
Only thing - your account data might (slight chance) be lost, keep that in mind.
If you’re coming from 2.2 ROM – Factory reset is needed. Absolutely.
Standard procedure after flashing zip update:
Wipe Dalvik cache.
Wipe Cache partition.
Fix permissions.
After first boot your home will blink and third party apps installed in data space. This is absolutely normal and intended.
--
DSC ROM "flash me before installing" pack.
[email protected]
Extract it to some folder and run flash(flash.cmd). Instructions provided in batch file itself.
Got flashing leds after flashing ROM? This will fix it.
--
DSC ROM 366 BB and DSP flasher (only for DSC 1.2 and above)
[email protected]
Extract it to some folder and run flash(flash.cmd). Instructions provided in batch file itself.
--
Stage UIhttp://n0p.8bit.fm/streak/DSC_StageUI.zip
Ripped from 406 ROM, but note that you can remove it later by simply uninstalling via standard menu
Phone button works for me.
--
In case you need original 406 ROM:
Olleh 406 ROM, Recovery to flash 406.
--
Add-ons:
Small russian letters on English Swype keyboard in landscape
--
Quickoffice
Themes: (Warning: themes under hide tag are incompatible with DSC > v1.2)Traveller ICS Theme
lordmorphous's Red and Blue
--
nickshertzer's Touch of ICS
--
Standalone wway's GingerTrue v1.1
(can be used to revert to stock DSC theme)
--
wway's GingerTrue Light * Version W/O CRT Animation
--
_2bad4u_'s MattedBlues
Quick solutions:
Use ClockSync! Set it to every 15 or 30 min on any possible connection.
--
Don't forget to launch DSConfig and see what you can configure!
--
Have WiFi problem? Enable built-in Wifi fixer or hPa's patched driver in DSConfig. Or try Wifi Reassociate.
--
Old info: Look here and say thank you to uglyrooster for his efforts.
Also - see this and this
WiFi Fixer may be a simpler and better solution for you. Origin.
--
Tip from attila.m: If cannot lower in-call volume, simply raise it to maximum and then to desired level.
--
Handset volume too loud? Use DSC Gain tool.
--
If you can't end conversation or press buttons in dialer.
Also - you can wave hand over proximity sensor (near speaker), screen will be unlocked after going off and on. Fixed.
--
Using generic cable? Look here.
--
Useful advice from btvbtv
--
Dolphin HD tip from streakOwner
--
Camera has white screen preview? Change debug.composition.type parameter in /system/build.prop to mdp
Setting can be changed with DSConfig.
--
Have flashplayer video streaming problems? AdFree might be the culprit.
--
Rogers tethering.
--
Bluetooth pairing problems?
--
Waking Streak by any button.
Changelog:
22.01.2013 - v2.3 Released Release post.
24.12.2012 - v2.2 Released Release post. Merry Christmas!
05.12.2012 - v2.1 Released Release post.
27.11.2012 - v2.0.1 Released Release post.
23.11.2012 - v2.0 Released Release post.
29.10.2012 - v1.7 Released Release post.
15.10.2012 - v1.6 Released Release post.
11.09.2012 - v1.5 Released Release post.
16.08.2012 - v1.4 Released Release post.
31.07.2012 - v1.3 Updated Release post.
30.07.2012 - v1.3 Released Release post.
18.07.2012 - v1.2 Updated Release post.
17.07.2012 - v1.2 Released Release post.
14.05.2012 - v1.1 Released Release post.
26.03.2012 - v1.0 Released Release post.
23.03.2012 - v1.0 Testing Open test.
19.03.2012 - v0.74 Testing Open test.
27.02.2012 - v0.73 Released Release post.
09.02.2012 - v0.72 Released Release post.
30.01.2012 - v0.71 Released Release post.
17.01.2012 - v0.7 Released Release post.
16.01.2012 - v0.7 open test Release post.
16.01.2012 - v0.7b-pre-3 Release post.
13.01.2012 - v0.7b-pre-2 Release post.
12.01.2012 - v0.7b-pre-1 Release post.
05.01.2012 - v0.66b Release post.
28.12.2011 - v0.65b Release post.
21.12.2011 - v0.64b Release post.
14.12.2011 - v0.63b Release post.
05.12.2011 - v0.62b Release post.
25.11.2011 - v0.61b Release post.
21.11.2011 - v0.6b Release post.
11.11.2011 (11.11.11) - To keep this date and to whose experiencing troubles with v0.54b:
v0.55b.
CPU governor set to conservative.
New streakOwner's tweaks.
wpa_supplicant.conf changed back.
10.11.2011 - v0.54b:
I'd consider this release as experimental, due to the following:
1. CPU lowest frequency is set to 128MHz. This frequency also works on even lower power consumption. streakOwner's idea that proved it's usefullness. Again
2. WiFi watchdog removed, as it consumes energy without actually helping the problem.
3. Change in wpa_supplicant.conf (to eth0), that at least seems to help uglyrooster, while not breaking anything.
4. New, revised version of tweaks by streakOwner
5. As a side effect of my USSD/Tether research - framework contains less Olleh/KT code, but it only make size smaller.
--
I would like to have any report of any regression here or in PM.
Thank you.
06.11.2011 - v0.53b:
GingerTrue theme v1.1.
Enforced internal WiFi watchdog.
Battery level on lock screen.
streakOwner tweaks.
02.11.2011 - v0.52b - Quick change - screen now turns on after disconnecting power (test-me SoD workaround)
01.11.2011 - v0.51b - Kernel undervolted (direct binary hack).
29.10.2011 - v0.5b - branch merge. New system framework from 406 Olleh ROM used.
28.10.2011 - v0.34b - Latest kernel from Olleh used.
27.10.2011 - v0.33b/0.42b - Factory Reset was causing a boot loop. Fixed.
25.10.2011 - v0.41b. Put back memory management from v0.3b-v0.32b
25.10.2011 - v0.4b. Added DJ_Steve's kernel.
24.10.2011 - v0.32b. Hardware UI acceleration enabled. CRT animation enabled (just for fun)
22.10.2011 - First public release (v0.31b)
Wishlist/ToDo:
Clean
Instructions by SJackalFirst install
1. Charge Streak to 100%
2. Copy DSC_v1.0 to root SD card
3. Get streak into Fastboot, (don't plug usb connector to pc, power on with Camera button pressed. Wait 20 sec, then plug usb connector)
4. Run flash.bat from 'DSC_flashme2' folder via command prompt, and follow all instructions
5. When rebooting, immediately press both Volume buttons to enter the Dell menu
6. With the Volume button navigate to the second option, 'upgrade...', and select by pressing the Camera button
7. The StreakMod menu appears, navigate to 'update using zip', then select the DSC_v1.0.zip file
8. When done, navigate back to the first screen, (back button), and select to reboot
9. While rebooting, again press both Volume buttons and when entered the Dell menu, choose the first option to Factory reset
10. And then wait for a long time
Updates
1. Copy updDSCvx.x.zip to root of SD card
2. Make sure battery is charged at 100%, and that usb is still connected
3. Shutdown and power on with both Volume buttons pressed
4. In the Dell menu, with the Volume buttons choose second option, 'upgrade...'
5. In the StreakMod menu navigate to 'update using zip', then select the updDSCvx.x.zip file
6. When finished, in the StreakMod menu's (also Advanced section), wipe the Dalvik-cache, Cache partition, Fix permission, and optionally wipe the Battery data
7. When finished, navigate back to the first screen using the back button, and select to reboot
8. Unplug the usb connector when the reboot starts
9. And then wait a few minutes
--
Quick flashing the ROM:Instructions for fast flashing:
DSC ROM "flash me before installing" pack.
[email protected]
Extract it to some folder and run flash(flash.cmd). Instructions provided in batch file itself.
Then flash latest ROM and update.
--
Guides:1.Guidelines for migrating from previous releases of DSC Roms.
Since you are already using a version of DSC (Dell Streak Community) you know how to do upgrade, just a reminder please dont neglect, do a dalvik-cache wipe, a cache partition wipe and a fix permission from the StreakMod advanced menu.
Optional, you can also recalibrate your battery by wiping battery data, while you are still flashing things , but be sure the battery was at 100 % before you stared flashing the updates and that the usb is still connected at the time of instalation, once you reboot, remove the usb cable and dont forget to let the first time your battery to drain out totaly until the phone shuts down by itself.
2.Guidelines for migrating form other Gingerbread based ROMs.
Coming from other Gingerbread Custom ROMs to DSC you need to be sure that you have the latest baseband 406 installed already,if you dont know which one you are actually using you can check easily on your phone, find Settings/About Phone/ and check the Baseband version (7th row), should read something like GAUSB1A140614-XX, if you dont see the 406 numbers than you have to update your baseband, as DSC requires and is tested to work with the latest 406 from Dell. To be sure nothing will go wrong during the flashing, it is highly adviced and recommended to use the DSC_flashme2.zip provided by (_n0p_) this way the human error during the flashing process is omitted. All you need is working Windows installation (32bit versions are tested) and the latest drivers form Dell installed on the PC. You need to extract the content of the zip file on any folder you like or the default folder offered by the system, DSC_flashme , but be sure to be easily accesed, you can remove the folder to any place you like after the flashing process, but since the adb.exe sits there , better dont delete it since logcats are highly apprechiated by the DSC team, to find out and erradicate bugs and problems. After the folder is in place , locate the flash.bat and double click on it, a windows DOS terminal will open, the instructions are clear for you , since you are supposedly familiar with such procedure before.
After the first reboot, continue with StreakMod menu to flash DSC which you have already put on your SDcard beforehand. You are required to wipe dalvik, wipe cache partitions and fix permissions before you conntinue with the reboot, due to changes between kernels used in different customs ROMs you are required to calibrate your battery first thing after the system boots.
3.Guide for migrating from Custom Froyo ROMs.
Many of the things are the same as above " Migrating form Other Gingerbread based ROMs", such as the upgrading of the Baseband files, the procedure is the same, note that some apps arent optimised or you might have trouble running them in GB , that is a issue you have to deal with your application developer.
4.Guidelines for migrating from Stock Froyo ROMs.
Running a custom ROM has its advantages and disadvantage (you woid your warranty), advantages are many thou nandroid backups, speed , flexibility, root ability, imporved battery life, tweaks to make your Streak do more than you are used to, quick response from the devs for daily issues etc.
Custom ROMs dont come in .pkg format as do OTA from Dell, but custom ROMs do come in .zip files, which then need to be flashed (installed) into your Streak.To make this possible you need first to install a modified image called StreakMod which would make it possible for you to install DSC. StreakMod is provided also from DSC in the pack DSC_flashme2.zip provided by (_n0p_).
Download the DSC_flashme2.zip provided by (_n0p_) All you need is working Windows installation (32bit versions are tested) and the latest drivers form Dell installed on the PC.
You need to download the main DSC ROM only form the links provided on the first post of DSC in XDA thread, copy it on the root of your SDcard where they can be easily accesed, or you can open a folder called DSC, and you can put there all the zip files from DSC, but remmember the place , as you will need to find those files later from StreakMod menu.
You need to extract the content of the DSC_flashme2.zip file on any folder you like or the default folder offered by the system, DSC_flashme , but be sure to be easily accesed, you can remove the folder to any place you like after the flashing process,
Now be sure you have charged your streak to 100% before you start installing DSC. DO NOT connect your Streak with the PC using the usb connector yet. Power your streak on and immedialty press the camera button, you will see a white screen, this is called the FASTBOOT mode "Wait for SD detect...." then you will see "FastBoot" tap on it and the streak will enter the FastBoot-Mode , you will see "Wait for USB FastBoot detect ...." wait 20 seconds then plug your usb connector to the mobile and after some seconds you will see "FASTBOOT_MODE", now you are ready to turn to your PC again and .....
After the folder is in place, locate the flash.bat and double click on it, a windows DOS terminal will open, follow the instructions there and reboot immediatly after you see the Dell logo within seconds you need to press and keep pressed both volume butons on the side of and then you will have access to Dell menu, select the second option by using the Volume buttons to go up and down the menu, once the second choice "upgrade...." press the camera button and wait several seconds, then a Dell logo with a triangle will appear, that is the StreakMod menu, try navigating the menu up and down with the volume buttons, and once second choice there " update using zip" is highlighted, press the camera button , then you will go to a another menu , where using the same volume buttons , you can navigate thru to find the place where you uploaded the DSC zip file , then once highlaghted press the camara button again and you will see the DSC_script doing its job, once finished , you need to press back button, and go back to the first menu where you select reboot. Once streak is rebooting agian keep your fingers press on both volume buttons, where you will see the Dell menu, now chose the first option, factory reset,streak will reboot by itself, let it reboot , you will see Dell logo, and then the DSC boot animation, wait now patience, if you have done all the above , nothing can go wrong, wait a little , then wait some more , bcs a lot of files is being genearated for first time, etc so this process can take some time, 15 minutes, if you have seen the DSC boot animation, it means everything is ok, otherwise you need to repeat the process again.
--
Manual flashing instructions:Find and download 407 Olleh ROM and corresponding recovery.
Rename 407 .pkg to update.pkg. Rename 407 recovery to recovery407.img
Get StreakMod recovery. Rename StreakMod recovery to recoverysm.img
Put recovery407.img and recoverysm.img to folder with your fastboot tools.
Download DSCv1.0.zip.
Download latest update - updDSCv1.1.zip.
Connect Streak to PC.
Copy update.pkg, DSCv1.0.zip and latest DSC update to SD card of your Streak.
Reboot. When Dell logo appears, press and hold Camera button. Select FASTBOOT.
Issue this commands using Windows command console (cmd.exe) - you should do a "cd PATH_TO_FASTBOOT_TOOLS%" first.
Code:
fastboot -i 0x413c flash recovery recovery407.img
fastboot -i 0x413c reboot
Don't close the command line.
Streak will reboot, now on Dell logo press and hold both volume buttons.
Select "2. Update...". Be patient while 407 ROM is flashing. Note that volume buttons are used as cursor arrows and Camera button as Confirm.
After 407 ROM is installed, Streak will reboot. Press and hold Camera button again when Dell logo appears. Select FASTBOOT.
Issue this commands using Windows command console.
Code:
fastboot -i 0x413c flash recovery recoverysm.img
fastboot -i 0x413c reboot
Streak will reboot, now on Dell logo press and hold both volume buttons (this time we have StreakMod recovery installed).
Select "2. Update...". StreakMod recovery will boot.
Flash DSCv1.0.zip.
Flash latest update (updDSCv1.1.zip).
Reboot, on Dell logo press and hold both volume buttons. This time select "1. Factory reset"
You set!
--
Help us, sending bugreports:Connect Streak to PC.
Dump log (i assume if you have flashed this ROM, you know what "adb" command is):
Code:
adb logcat -d >mylog.txt
If bug causes Streak to reboot, do this:
Connect Streak to PC, issue command:
Code:
adb logcat >mylog.txt
and try to reproduce the issue. (adb will automatically disconnect on reboot).
Send me "mylog.txt" or attach to this thread.
My e-mail is n0p[at]ukr[dot]net
I don't promise immediate responce, but this log would be very helpful.
Thank you for attention.
Thanks for giving us another choice of rom.
Have you got any screenshots and what overclock are we talking?
Method is described here: http://forum.xda-developers.com/showthread.php?t=1302831
Will make some screens soon.
have you seen Dell released kernel for 2.3.5 on dell open source? this may help with your ROm and bugfixes..
good to see more development.
chrisrotolo, you could've noticed that i've replied in that thread
I think either watch_mania or DJ_Steve will release something big soon.
Right now i'm moving, and gonna be in that state for a month and just don't have time for that. But'd really love to.
Downloading this now.... this coming from fards gs 2.4 so can i keep same amss or the one in op is different ?
Sent from my Dell Streak using XDA App
If your baseband number shows 40514-EU - you can keep your current one.
Is it also possible to disable the battery cover sensor for this ROM? That would complete my wishlist
This could be done. I'll take a look on my free time, if i'll have any
To my knowledge only SimpleStreak has this feature. Would be great if we could get it on more ROMs
NO Internet...
Everything seems to be working great. The OC makes it a little snappier, at least enough to notice it... just having ONE problem though, I don't have any connectivity... I have a wifi signal but it won't connect, it says connected in the settings but I can't browse or connect to anything that needs internet. Same situation with 3G, but with 3G I don't even get the wireless symbol in the status bar..
cdzo72, that's quite odd.
Can you dump and send me or attach here the log?
When Streak is connected to PC, issue this command:
Code:
adb logcat -d >mylog.txt
My e-mail is n0p[at]ukr[dot]net
_n0p_ said:
cdzo72, that's quite odd.
Can you dump and send me or attach here the log?
When Streak is connected to PC, issue this command:
Code:
adb logcat -d >mylog.txt
My e-mail is n0p[at]ukr[dot]net
Click to expand...
Click to collapse
Gimme a couple days... I immediately nandroided back to my install of 2.4... I'll try this one again in a couple of days when I get a couple of hours of spare time...
I tried flashing the amss and dsp1 files for Steve and fards build but it didn't help, and oddly enough when I nandroided back to their build, I had to reboot twice before I could regain connectivitiy... like you said, quite odd
2 days with this Rom and quite satisfied. I have random reboots these seem to occur only After the processor has completed some heavy tasks I.e online flash content. Example I drove 3 hours using sygic navigator and never had a problem then I closed sygic and removed car power adapter checked 2 minutes later the screen was black and had to remove the battery as it didn't turn on anymore.
What I like about this rom is that it is quick and the dell stage removed, the battery's percentage and the phone apk is ok with higher dpi and overall apart the reboots mentioned seems stable enough for day use. Please keep track of the new updates and post them.
Sent from my Dell Streak using XDA App
I would really like to see the log.
Could you connect Streak to PC, issue command:
adb logcat >mylog.txt
and try to reproduce the issue?
adb will automatically disconnect on reboot.
Just to let know that downloads are right now limited to 30KBps/15 sessions.
_n0p_ said:
cdzo72, that's quite odd.
Can you dump and send me or attach here the log?
When Streak is connected to PC, issue this command:
Code:
adb logcat -d >mylog.txt
My e-mail is n0p[at]ukr[dot]net
Click to expand...
Click to collapse
Sorry I didn't get you the logs, it may have been a phone problem... when I nandroided back to my original Gingerbread I couldn't connect either so I flashed the amss and dsp1 and still had no luck.... so I went back to bare stock and started from scratch and now I am able to connect...
BUT have run across another issue, I can update the Superuser app but it won't update the binary... so I manually replaced it and then wasn't able to use any apps that needed root... so I put the old one back, still no root; I had to flash the ROM again to be able to use ROOT apps
_n0p_ said:
cdzo72, that's quite odd.
Can you dump and send me or attach here the log?
When Streak is connected to PC, issue this command:
Code:
adb logcat -d >mylog.txt
My e-mail is n0p[at]ukr[dot]net
Click to expand...
Click to collapse
Still having problems with the wifi and 3g connectivity so here is the log you asked for.. thanks for taking the time..
mylog.txt
cdzo72 said:
Still having problems with the wifi and 3g connectivity so here is the log you asked for.. thanks for taking the time..
mylog.txt
Click to expand...
Click to collapse
What do i clearly see - that's not a log of clean install.
Application permissions are broken, for start.
How did you migrate to this ROM?
--
If you want to upgrade Superuser+su, which i don't recommend, update busybox first and make sure it supports "busybox which" command.
CM10 "Jelly Bean" for
Samsung Wave I (GT-S8500) & Wave II (GT-S8530)
Alpha 0.32 Release
“Seriously, Don’t Try To Sell This... You’ll Really, REALLY Regret It” Edition
Hey all,
So once again it’s time. Introducing the first alpha development preview of CyanogenMod 10 (based on Jelly Bean) for the Samsung Wave.
This preview is intended only for developers as it is in a very early development stage and not all features of the device are fully working.
Let’s emphasize that-- THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DOESN’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.
FAQ IS RIGHT HERE, CLICK AND READ BEFORE POSTING
WHAT DOESN’T WORK (BUGS/TODO)
Most of the modem (GSM/GPRS) functionallity because there's proprietary protocol between Bada and AMSS used, not implemented in any known Android RIL.
GPS - heavily related with above, as GPS chip is wired to Call Processor
Microphone - most likely related to modem - appears to be controlled by AMSS at some part
Magnetometer (Compass) - haven't looked into it carefully yet
Proximity sensor - haven't looked into it carefully yet
WHAT DOES (SHOULD) WORK
Sound playback
Screen
Wifi/BT
Accelerometer
Camera
Camera LED
Battery Gauge Warning: Don't leave it charging without supervising - if it gets enormously hot, disconnect it - this can literally blow up battery as there is no overheating protection yet. Do not leave it connected on 100% - it'll discharge by 1% all the time, and then recharge, what's very unhealthy for battery.
SUPPORT
You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it, use Bada or other releases.
We basically lack time to give full dedication to this rom, and we’re looking for skilled devs who know the Android, and/or other things that might be relevant.
Please join us on IRC: some people are on #badadroid (freenode).
BUG REPORTS
This is the format for a bug report: “XXXXX isn’t working. Here is how to fix it: [INCLUDE SOLUTION]” Don’t have source? Too bad. You’ll have to wait then.
If you report bugs, please don’t be disappointed if we can’t fix them immediately (or even never). It’s not because we don’t care, but because we don’t have time or don’t know how to fix it.
Please attach logcat and dmesg dump in your bug report. Dmesg should contain messages from both - bootup and issue occuring (you can't dump it 1 hour after bootup, rather 2 minutes after)
How to dump logs - Google for "android logcat dmesg" Or... whatever, here's one of 3204109 methods available.
In the Terminal Emulator enter:
"su"
Accept request for SuperUser access.
"dmesg > /emmc/dmesg.log"
"logcat -b system -b radio -b events -b main > /emmc/logcat.log"
Download them from phone, archive and upload them.
Note: You might need to change /emmc/ to /tmp/, /sdcard/, or something that will help you obtaining these logs.
Privacy warning: Your logcat might contain sensitive information like your IMEI, IMSI, cell stations you were nearby, numbers you called and got calls from and SMS sent and received. If you don't want to publish this info - send them privately to one of developers.
Click to expand...
Click to collapse
If the Badadroid is restarting before you're able to catch any log:
Download http://goo.im/devs/Rebellos/wave/bterm.exe
Try to start kernel normally, when you see Badadroid logo start holding the middle key pressed. Keep the middle key pressed until phone restarts and shows the text: FOTA DOWNLOAD MODE & bTerm
Connect phone to PC.
Start bterm.exe
Type 4 commands:
Code:
open
dumpram 0x4FF00000 0x100000
close
exit
There should appear file called dump_ram_0x4FF00000.0x00100000.bin - pack it and attach it to your bug report.
Click to expand...
Click to collapse
Bug reports without logs are completely useless.
NOTE: DEVELOPERS WANTED. Please contact us if you are a developer with something to contribute.
I do heavily encourage to work together on the better, common project instead of making kang releases and demanding money for somebody else's work.
Read as: If you think you can make something better than this by doing less and muchazo Ctrl+C Ctrl+V - you suck, go figure the rest.
HOW TO BUILD
I do recommend perfect tutorial by fattire: https://docs.google.com/document/d/19f7Z1rxJHa5grNlNFSkh7hQ0LmDOuPdKMQUg8HFiyzs/edit?hl=en_US
Of course you have to init with -b jellybean and modify some steps.
local manifest to use: https://raw.github.com/Rebell/android_wave_local_manifest/jellybean/local_manifest.xml
I do it like this:
Code:
cd ~
mkdir wave
cd wave
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
cd .repo
wget https://raw.github.com/Rebell/android_wave_local_manifest/jellybean/local_manifest.xml
cd ..
repo sync -j8
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
brunch wave
device name is wave so the build invocation can be brunch wave
FIRST INSTALLATION
Bada 2.0 is required
Enter Bada Settings->General->Memory and make sure you have at least:
370MB of free "System" memory
150MB of free "User" memory
400MB of free "Applications" memory
Download 3 packages: BOOTFILES, armlinux_boot and selected release for your device (please pay attention if it's S8500 or S8530 BOOTFILES and FOTA you're choosing!):
Releases: http://goo.im/devs/Rebellos/wave
Start Bada.
Extract zImage from zip and copy it to the Bada's User partition (the one about 390MB big).
Copy whole .zip to the Bada's User partition.
Flash BOOTFILES and FOTA using Multiloader.
If you have been already using my FOTA bootloaders, you don't need to flash BOOTFILES.
Reboot the phone holding Power and Call key.
FOTA set of red messages should appear, after about 15seconds Badadroid logo shows up.
Be patient, first bootup will keep unresponsible on Badadroid logo for up to 5 minutes.
CWM Recovery starts, pick:
- install zip from sdcard
- choose zip from sdcard
- cm-10-wave-<release id>.zip
- Yes - install
Reboot holding the Power key
You can remove installation .zip from the User partition from Android level by connecting through USB in MTP mode.
Do not remove zImage file and modem directory.
Normal bootup is available using Power+Call keys
CWM Recovery mode is available using Power+Volume Up keys
CWM Flashing does overwrite zImage. So every next update you can just flash .zip through CWM.
HOW TO UNINSTALL
Follow the steps there: http://forum.xda-developers.com/showpost.php?p=35107469&postcount=393 (thanks Volk204)
THANKS TO
Oleg_k, mijoma, nbates66, anghelyi, Volk204, mikegapinski, hunktb, autra, Tigrouzen and many others.
Special thanks to chrmhoffmann for letting me kang his release description.
CHANGELOG
Releases available there: http://goo.im/devs/Rebellos/wave
0.32 - original releasenotes and link http://forum.xda-developers.com/showpost.php?p=41131519&postcount=2408 - courtesy of Volk204
Incorrect LCD type detection in S8530 with HWREV 0x5 has been fixed. LCD should work on ~99% of Waves 2. (Thanks to Rebellos)
Bluetooth MAC is correct.
Modem directory moved to /data/radio (experimental patch)
RIL: Fixed handling SMSC number in national format
Corrections to the key mapping. Still to be polished. Call key as BACK, Middle as MENU, long press - recent apps, End Call as ENDCALL, long press show power off menu (fixed correct power off process), short press "Go to Home"(it is not real HOME key, but it revert to HOME screen in most of cases), lock as HOLD - only screen on/off (framework patch)
Key mapping visualisation: http://img203.imageshack.us/img203/6838/badadroidv032.jpg
Upstream CM patches.
0.31
Screen waking up has been fixed for S8530 with LCD type 3. (kernel only update, thanks to Volk204 for providing a quick fix, people with working S8530 screen doesn't need to update!)
You can overwrite only zImage on bada_user partition if you don't want to download whole zip.
0.3
Fixed fetching incorrect NITZ date and time when network didn't provide proper data (like 1971/1/1/ 01:00:00).
Fixed showing up No signal/Network unavailable when phone did actually register into network.
Proximity sensor is working. There's no light sensor in Wave.
Compass is working. Might need some further calibration.
USSD requests are working. (Network codes like *#1234# to check your account balance etc.)
Basic outgoing calls are possible. NO SOUND YET
RIL logs has been moved from systemlog to radiolog - In future reports please attach all logs! I updated logcat fetching instructions.
SIM recognition and detection in most of the cases should be fixed.
Preferred network mode (2G/3G) selection. (Probably the choice won't persist between restarts)
S8530 screen is waking up properly now. Couldn't test it on S8530 with screen type 3, so this might need a fix for these.
Random screen crash due to MMC driver going crazy should be fixed on some boards - it MIGHT cause issues on other boards - it'd be visible on dmesg.
Experimental Samsung RIL Socket (originally done by Paul Kocialkowski) utilisation to control calling sound pathes. More to come in next releases.
Better S8500 touchscreen calibration (thanks to Tigrouzen)
Airplane mode
0.2
Almost all of the features in this release were implemented by Volk204, send him a big beer.
Real IMEI reading out of NVdata.
SIM card unlocking with PIN.
Registering to mobile network.
Incoming call support, answer/hangup option. NO AUDIO RECEIVING OR SENDING DURING CALL YET No outgoing calls yet.
Receiving SMS.
Sending SMS.
Time from network updates (NITZ)
Tons of other important things you won't even notice nor imagine how much effort did it take.
Upstream CM10 changes.
0.1
FOTAs update is required to the version with "for_0_07" name.
To update from older versions - first manually unpack zImage from archive just like during first installation, then after rebooting you can continue installation.
Kernel and platform are now unified for both Wave1 and Wave2 - only FOTA used does differ between models.
SD Card should get detected on all of the devices now.
Fixed backlight on Wave2 - LCD waking up is still not working properly.
Fixed kernel panic due to WiFi initialization fault - thanks Volk204.
WiFi is working on Wave2 now - thanks chemosun
Much better HW key handling - big kudos to Volk204.
Increased system partition size to 375MB (should be big enough to fit GApps in it now and leave some "living space")
Implemented experimental battery charger and fuel gauge driver - Warning: Don't leave it charging without supervising - if it gets enormously hot, disconnect it - this can literally blow up battery as there is no overheating protection yet.
Do not leave it connected on 100% - it'll discharge by 1% all the time, and then recharge, what's very unhealthy for battery.
Included Mocha-IPC and Mocha-RIL drivers, very basic, very buggy, but should bootup modem into Low-Power-Mode and read battery status. (C CODERS WANTED)
Fixed mounting of internal sd card as main storage - it should be possible to fully use features like Market and Camera without external-SD card.
CM10 mainline patches.
FOTA bootloader does now support recovery boot by holding volume-up key only (no need to hold middle key anymore). Needs update of FOTA.
Enabled overclocking to 1.2GHz and 1.4GHz. <Volk204>
JPEG buffers patch from Aries, so there's even more RAM available (~250MB) <Volk204>
Fixed "Advanced Settings" derived from Galaxy S. <Volk204>
Fixed TVOut. <Volk204>
Simple IO scheduler pulled from Aries. <Volk204>
Vibrator intensity control from Aries. <Volk204>
0.07
Not released, renamed to 0.1
0.06
Reworked whole installation procedure, .imgs relocated and resized.
Cache(18MB) + System(250MB) goes to bada_private partition
Data(400MB) goes to bada_apps.
zImage is kept on bada_user (390MB), bada_user also becomes user storage (internal sd card) on Android, so it's shared with Bada
Pulled Torch fix into release. (Herpderp me, forgot it in 0.05)
Cleaned up unnecessary things in platform (auto-brightness for example)
Recovery should be fully working by now. Including flashing things like gapps and stuff. (gapps: http://goo.im/gapps/gapps-jb-20121011-signed.zip )
0.05
Fixed screen problems on S8500. Thanks to Volk204.
LED flash is working, together with Torch apk. Thanks to Volk204.
29MB RAM more is available to the userspace now. Again, thanks Volk204.
Improved S8530 touchscreen calibration.
Improved S8530 backlight regulation levels.
Latest CM10 changes.
FOTA has been updated, it does produce debug output to the screen instead of UART, this should help debugging "won't bootup" troubles.
FOTA and BOOTFILES are included in .zips
0.04
Added support for S8530, thanks to Tigrouzen and Volk204 for testing and support. Please report bugs in LCD driver in this thread, Wifi is not working yet
Latest CM10 source base (including goodies like CM File Manager)
0.03
Platform is starting up! And pretty stable.
Synced with CM Aries kernel sources.
New FOTA is recommended.
0.02
Got working recovery, new kernel initramfs structure.
0.01
Initial release.
MORE LINKS
Overall project thread - http://forum.xda-developers.com/showthread.php?t=1459391
Hi Rebellos,
I just registered for your project, I'm interrested in. I'm new to all this things, like customs firmware etc. I've tested the Android 4 ICS on Wave S8500 and the missing thing is just Modem (GSM?).
I'm very interrested in your project. I want to test it, but. I'm just a noob in this all things like I've said it... I very want a functional Android on Wave S8500. So, keep it this great work please!
Thanks you.
Sorry for my bad English sir.
its always stuck at badadroid boot image
tried with both
Mikegapinski release and anghelyi's release
not able to boot into jelly bean
yeah! Rebellos is best!
stuck at boot.
but 4.0.4 slim is still better than this release
I've uploaded new package and updated link. Hope now it does contain correct image.
@Up:
U say? Sherlock.
Rebellos said:
I've uploaded new package and updated link. Hope now it does contain correct image.
@Up:
U say? Sherlock.
Click to expand...
Click to collapse
stucks on boot logo.
but im not sure whats the problem, the system file or the zImage file.
can someone give me a work zImage file?
Rebellos said:
I've uploaded new package and updated link. Hope now it does contain correct image.
@Up:
U say? Sherlock.
Click to expand...
Click to collapse
Again bad img
I rechecked previous and this release and both .img works for me. So updated link once again. This time archive does contain zImage I'm using aswell.
PS: Remember you are welcome to join #badadroid if you got some patches or are just seeking for friends.
Rebellos said:
I rechecked previous and this release and both .img works for me. So updated link once again. This time archive does contain zImage I'm using aswell.
PS: Remember you are welcome to join #badadroid if you got some patches or are just seeking for friends.
Click to expand...
Click to collapse
I'll try it now.
THANK AGAIN!
Rebellos said:
I rechecked previous and this release and both .img works for me. So updated link once again. This time archive does contain zImage I'm using aswell.
PS: Remember you are welcome to join #badadroid if you got some patches or are just seeking for friends.
Click to expand...
Click to collapse
Hi Rebellos
the same is with new system.img
Could you please upload img without archiving? Probably problem is with your archiver
shaiws said:
stucks on boot logo.
but im not sure whats the problem, the system file or the zImage file.
can someone give me a work zImage file?
Click to expand...
Click to collapse
Here you have everything you need, the initramfs is the zImage without compiling.
https://github.com/Rebell/bdroid
best regards.
Initramfs is part of zImage, not zImage itself.
I don't know why your tries are stuck. Remember you need cache and data images too.
There are unpacked files http://goo.im/devs/Rebellos/cm10-wave-0.01/
My first attempt was only with system.img and zimage and, of course, I got stuck on the Badadroid logo screen too.
Second attempt I also copied cache and data images from my working "Polishblood" image. It also gets stuck on the logo screen.
Haven't tryied the unpacked files yet. But I didn't receive any error messages when extracting the packed ones.
Rebellos said:
Initramfs is part of zImage, not zImage itself.
I don't know why your tries are stuck. Remember you need cache and data images too.
There are unpacked files
Click to expand...
Click to collapse
Dear Rebellos, i have tried your packed version and unpacked version with no luck. I just stuck at badadroid logo.
In your opinion, what would be the problems?
mikegapinski version and slim version work well in my wave. I have included all file needed but i get no luck with yours.
Maybe that you are using different bootloader or you do something with the bootloader? I not rushing anything, i am just eager to test your jellybean build. I am aware that it will be slow and lack of many features but it does not stopping me to try out your build.
I am really happy that you spend your precious time and energy to make this build. i, one of wave owner, really appreciate your effort.
OK, I get this compilation error:
Code:
make: *** No rule to make target `vendor/samsung/wave-common/proprietary/cypress-touchkey.bin', needed by `out/target/product/wave/system/vendor/firmware/cypress-touchkey.bin'. Stop.
make: *** Waiting for unfinished jobs....
Confusing parts start in point #4 of fattire's tutorial:
4. Next, install the proprietary files per the original instructions and run the ./setup-makefiles.sh script in android/system/device/bn/encore.
Click to expand...
Click to collapse
There's no setup-makefiles.sh in android/system/device/wave/ no android/system/device/wave-common/ , although I suspect this part is not that important.
As there it says that
(if that doesn’t work for some reason, try typing add_lunch_combo cm_encore-userdebug manually.)
Click to expand...
Click to collapse
I tryied doing that and got same error. But I'd say that my first attempt took only half an hour or so, and on second attemp, after doing an add_lunch_combo cm_encore-userdebug, took significantly longer. Could that be possible?
I start the compilation process with a . build/envsetup.sh, than "brunch wave", but also I want to note that 1st time I made a . build/envsetup.sh then "lunch" and there I didn't find a "wave" in the list of devices.
well
tried 20 times now, nothing worked
its still stuck at boot image.
All
Files present in phone mem are
cache.img
datd.img
polishblood_Nightly1.img (rebellos's img renamed)
zImage (latest)
I also tried not renaming the systemimg to polishblood
all in vain
anybody else facing this problem??
deeps_17 said:
well
tried 20 times now, nothing worked
its still stuck at boot image.
All
Files present in phone mem are
cache.img
datd.img
polishblood_Nightly1.img (rebellos's img renamed)
zImage (latest)
I also tried not renaming the systemimg to polishblood
all in vain
anybody else facing this problem??
Click to expand...
Click to collapse
Same..
I think we should give to rebellos time, and we will get a working B
@Rebellos maybe you should uploud the all file that you are using in your wave.,,
Hello,
I've also tried to, but i'm stock at logo, also after i tried some photos and videos are missing from my SD Card.
It worked fine before with ICS.
Thanks anyway
system.img should not be renamed.
I've added clean system_cache.zip into http://goo.im/devs/Rebellos/cm10-wave-0.01/ though it's empty and JB seems to be stuck on boot animation with it. You might try first running ICS and then upgrading to JB image.
@Building issues:
I forgot to push one commit. Did it now so after "repo sync" you should be able to go.
CM Wiki, CM Google+, Fireball Wiki, Fireball Google+
Non-development related questions and troubleshooting belong here: [Q&T][ROM] CyanogenMod 10.1 and 10.2
Contents
This Post: Instructions and information - Please read all of this post before installing CyanogenMod!
Post 2 - Restoring a non-functioning radio
Post 3 - Frequently asked questions and workarounds for common problems
Introduction
This is CyanogenMod 10.2 (cm-10.2) for the HTC Droid Incredible 4G LTE (fireball) based on Android 4.3. Usage of this ROM indicates that you understand...
the warranty on your device is void;
the developer(s) are not responsible for any damages that may occur to your device as a result of using this ROM;
there is a significantly higher chance that your device will eat your cat (for which the developer will not take responsibility).
Preparations and Installation
Get your phone ready for a new ROM
You must have an unlocked bootloader or be S-OFF (read here for instructions)
Before leaving your stock based ROM:
Turn on all GPS location services: Settings > Location > (all three location services) = On
Change network mode to CDMA/LTE: Settings > Mobile Data > Preferred Network
Backup the contents of your internal sd card. You can ignore these files/folders: ext_sd, battery_history.txt, .android_secure
Install a custom recovery: CWM or TWRP
Make a backup of your current ROM in recovery - DO THIS!
Install CyanogenMod
Perform the factory reset function in recovery and additionally wipe the /system partition
Flash the CyanogenMod zip (do not flash gapps yet)
a) If you are S-OFF, you can reboot now.
b) If you are only unlocked, and not S-OFF, you will need to flash the boot image through fastboot. Extract boot.img from the zip file and place it in the same directory as your fastboot and adb executables. While still in recovery, execute these commands one at a time:
Code:
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
The first time CM boots, change the following network settings and then reboot:
Select LTE/CDMA/EvDo network mode: Settings > (Under Wireless & Networks) More... > Mobile networks > Preferred Network
Select RUIM/SIM subscription: Settings > (Under Wireless & Networks) More... > Mobile networks > CDMA subscription
(Optional) Reboot to recovery and flash the GApps version corresponding to CM 10.2.x
Note: many apps require Gapps to be installed before GPS will lock-on a location
Updating to a new build
Make a backup of your current build in recovery
Install the new build
If you are S-OFF, reboot
If you are S-ON and HTCDev Unlocked, reboot to the bootloader and flash boot.img using fastboot (extract it from the CyanogenMod zip)
Your settings and data will be preserved. You will get an "Android Upgrading" notice upon reboot which is nothing to worry about.
Special notes about connecting to Verizon's network
Getting the RIL to play nicely with Verizon is tricky. The following quirks should be noted:
Waiting for network...: If you install gapps, the phone might seem to hang at "Waiting for network... Activation can take a few minutes" on the first boot. This takes a long time to timeout (maybe 3-5min). When it eventually fails, choose the SKIP option. Do not choose restart or the cycle will repeat. This is a one-time inconvenience that should not reappear on subsequent reboots.
Borked radio: in the rare event that your radio refuses to make a connection, your radio's nv may have stored some bad settings. If restoring the backup of your previous ROM does not restore the radio to working condition, then see Post 2 for instructions on how to get the radio working again.
Official Downloads
Official builds are available at download.cyanogenmod.org/?device=fireball
Archive of older official nightlies: goo.im/devs/cm/fireball/nightly
There is currently a nasty little acpuclk bug that can cause boot-loops after rebooting the phone. A battery pull remedies this.
Unofficial Builds
These builds are not endorsed by CyanogenMod. They are my personal builds.
Most recent builds: goo.im
Archive/Mirror: mediafire.com
goo.im folder structure: visit the page to read release-specific notes
mdm-releases - Based on CM 10.1.2 stable using linux kernel 3.0
kernels - Enhanced kernels for use only in CM
cm-10.1 - CM 10.1 builds that incorporate experimental patches being considered for inclusion in official CM releases
cm-10.2 - CM 10.2 builds that incorporate experimental patches being considered for inclusion in official CM releases
GApps
Download the GApps version corresponding to CM 10.2.x
Reporting Issues and Getting Help
Policy on bug reports:
You must reproduce the issue in a clean state. i.e. install cm after wiping /data, /cache, and /system
logcat or GTFO
If these steps are not taken, your report will be ignored.
How to gather helpful data for troubleshooting
How to use the issue tracker
Getting help
There is an IRC chat room on freenode.net where you can speak with other HTC s4 and m7 users: #cm-htc. A device maintainer is usually present as well. For reference, the fireball is an s4 device in the same league as jewel (EVO 4G LTE), ville (One S), and evita (One XL), and these are all based on the Qualcomm Snapdragon S4 Plus MSM8960 processor. The various HTC One models for different carriers fall under the m7 name and use a similar but more advanced processor, the Qualcomm Snapdragon S4 Pro APQ8064. The device maintainers on s4 phones are: jewel=deck, evita=h8rift/rohan32, ville=intervigil, fireball=mdmower.
Change Log
CyanogenMod BBQLog
CyanogenMod CMXLog
fireball-specific changes:
20131107 - SMS messages no longer split at 160 characters
20131106 - fade-out animations fixed
20131029 - substantial radio updates, increase speakerphone mic volume, new power managment code in kernel
20131020 - speakerphone and headphone volumes adjusted
20131018 - usb tethering fixed, speakerphone mic fix, wake-on-volume fixed
20131015 - flickering panel fix
20130909 - initial(ish) release
Click to expand...
Click to collapse
Known Issues
Official Builds
Display flickers when brightness is set at max Workaround in post 3
Device boot-loops after restarting Workaround in post 3
High pitch background noise in camcorder recordings (only seems to affect some users)
Auto-brightness is slow to adjust after display-on
Many apps require Gapps to be installed before GPS will lock-on a location
Known Issues that will not be fixed
OTG mounting of USB sticks - Likely no hardware support
FM Radio - Likely no hardware support
MicroSD does not show as a mass storage drive when connected to the computer - UMS was deprecated in Android 3.x
Workaround in post 3
Development Information
The following trees are needed to build CyanogenMod 10.2
CyanogenMod/android_device_htc_fireball
CyanogenMod/android_device_htc_s4-common
CyanogenMod/android_device_htc_msm8960-common
CyanogenMod/android_kernel_htc_msm8960
Use the extract-files.sh script in the fireball device tree while running an official cm-10.2 build to pull necessary proprietary files into vendor/htc.
Credits
The task of bringing CyanogenMod to the HTC Droid Incredible 4G LTE was not a one man effort. I'm indebted to
htc-msm8960-devs: a talented group of developers with lots of patience while I was learning
utkanos, KemoNine, and Jin^eLD for general building questions
jose51197, Linch89, and blazingwolf for early testing reports
squeezyb for selling his fireball at a discount so I can share it with other developers
Restoring a borked radio
In the rare event that your radio refuses to make a connection, your radio's nv may have stored some bad settings. If restoring the backup of your previous ROM does not restore the radio to working condition, then follow these instructions to get the radio working again. This method is less invasive than running the RUU followed by a factory reset, as it will not overwrite hboot.
Downloads
Stock ROM
recovery_signed.img - MD5: e9334607c52aebe2da20c53c32820391
Instructions
From your preferred recovery, run the factory reset option
Follow the directions in this thread to install the stock ROM
Boot the ROM, then turn off HTC's fast boot: Settings > Power > Fast Boot = Off
Reboot to the bootloader
Flash the stock recovery:
Code:
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
Factory reset from the bootloader: BOOTLOADER > FACTORY RESET
Let the phone reset and boot up
Allow network connectivity to be restored (make a test call)
Turn on all GPS location services: Settings > Location > (all three location services) = On
Turn off HTC's fast boot: Settings > Power > Fast Boot = Off
Reboot to the bootloader
Flash your preferred recovery: CWM or TWRP
(If you just want to run this stock ROM, you can stop here)
From your preferred recovery, run the factory reset option
Restore your ROM backup and wipe cache again before rebooting
FAQ and Workarounds
The solution to many problems
Before installation, you really need to run the factory reset option in recovery. If you are the only person experiencing a problem, try this first. It cures many problems!
Stuck at the HTC boot screen
If you are only unlocked, and not S-OFF, you need to flash the boot image through fastboot. Extract boot.img from the zip file and run
Code:
fastboot flash boot boot.img
Enable USB debugging or access Developer Options
Settings > About phone > tap 'Build number' 7 times
Boot-loops
There is a known bug in acpuclk which affects all of the htc msm8960 devices. When you reboot your phone, it might crash at the CM logo and start boot-looping. This is the kernel panicking when it continuously fails to bring up cpu1. The workaround is a simple battery pull. It's pretty reliable. After CM loads, this bug doesn't affect the device.
Screen flicker
If you notice the screen flickering rapidly:
1) Make sure you're running build 20131015 or newer
2) Try lowering the brightness a bit or using auto-brightness - this usually only occurs when the brightness is set very high
3) If using auto-brightness, when you turn on the display, let the brightness settle before touching the screen
"SIM card added" or "Waiting on... activation" notice every time the phone boots
SIM card added notice: do not hit restart, just hit back and the notice will go away
Activation notice: just hit home and the notice will go away (if the home button does nothing, just wait it out for 3-5min and then choose the skip option).
"What mobile network settings should I use?"
Verizon Wireless users in the U.S.
Settings > More... (under Wireless & Networks) > Mobile networks:
Network mode = LTE/CDMA/EvDo
CDMA subscription = RUIM/SIM
Usage of this ROM on non-Verizon carriers is unsupported. That doesn't mean it won't work; it just means you won't get support from me to try and make it work. There are several users that use this phone either out of the country on GSM networks, or on prepaid carriers in the US. I just ask that discussion specific to these scenarios be kept in separate threads -- perhaps @jose51197 can start a thread and I'll link to it from here.
Missing menu button in applications
First, set this: Settings > Buttons > Allow custom buttons = True
Option 1: Re-associate the recent apps button: Settings > Buttons > Recents Button > Short press action = Open/close menu
Option 2: Use action overflow: Settings > Buttons > Menu button > Show action overflow = True
Text messages from 6250 with message VZWNM: #
See this thread and this post.
ext_sd doesn't show files on the MicroSD
ext_sd is a leftover folder from the stock ROM. It is not used in CM because it prevents the internal storage from mounting successfully to the computer in UMS mode. File managers for Android should set /storage as their home directory to access internal and external storage.
Examples:
ES File Explorer: Settings > Path Settings: Home Directory = /storage/
Root Explorer: Preferences > General Preferences: Home Folder = /storage/
ADB reports device offline
After connecting the phone to your computer via USB, accept the prompt on the phone to allow connections from your computer.
Sound is distorted when DSP presets and/or bass boost are enabled or
Gapless music playback doesn't work
Set lpa.decode=false in build.prop:
Step 1) Settings > Developer options > Root access: Apps and ADB
Step 2) Type these lines one at a time at a command prompt (do not copy/paste the whole block at once):
Code:
adb root
adb remount
adb shell
# Make sure you have a # prompt now. If $ prompt, the following will not work.
sed -i 's/lpa\.decode=true/lpa\.decode=false/g' /system/build.prop
exit
adb reboot
To revert this change later, perform the same steps above, but swap true and false in the sed line.
MicroSD will not mount as a mass storage drive when connected to the computer
UMS was deprecated in Honeycomb, so be appreciative that you can access your device at all through this method! You can use MTP connection mode if you need to access both internal and external storage:
Settings > Storage > (menu) USB computer connection > MTP
Windows and Mac recognize MTP devices automatically.
Linux requires a bit more work, here's the quick instructions:
edit /etc/udev/rules.d/51-android.rules to include these lines for adb and mtp:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
install gvfs-mtp; for Ubuntu (or Ubuntu based distributions) this can be done with:
Code:
sudo add-apt-repository ppa:langdalepl/gvfs-mtp
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install gvfs
Restart your computer
Phone number, MIN, and PRL do not show in phone status or
MMS messages don't send: "Invalid destination"
Go to Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription. Change the subscription type from NV to RUIM/SIM. Restart the phone.
GPS doesn't acquire a signal
From recovery, make a nandroid backup of CM
Wipe data, cache, and system
Restore a stock-based ROM backup
Enable all location services: Settings > Location > (all three location services) = On
Use a GPS application to get a lock on your position (I use GPS Test)
From recovery, wipe data, cache, and system
Restore CM backup
Wipe cache and Dalvik cache
Internal storage is not accessible by ROM or recovery
This rarely happens and unfortunately only seems to be remedied by formatting the internal storage:
Restart the phone to recovery and connect the USB cable to a Windows computer
In recovery, use the mount USB feature:
ClockworkMod(-based): mounts and storage > mount USB storage
TWRP: Mount > Mount USB Storage
When Windows informs you that it needs to format the drive in order to recognize it, go ahead and format it as FAT32
After the format is complete, use the safe eject feature in Windows followed by unmounting the USB storage in recovery
Your /sdcard partition should now be accessible
Encryption
Pre-requisites: TWRP 2.6.0.0 or newer
Encryption procedure:
Make a full backup in TWRP
Restore /data from your backup - This seemingly odd step will ensure a footer is allocated at the end of the /data partition for encryption information.
Reboot and let phone battery charge to 100%
Turn on Airplane mode
Settings > Security > Encrypt phone
Be patient, your screen may go black for a couple minutes without indication of anything occurring before a reboot occurs and encryption progress is displayed.
Reverting encryption:
Make a full backup in TWRP (you will need to enter your encryption PIN upon entering recovery)
Reboot to TWRP, but instead of entering your encryption pin, just hit cancel
Wipe your data partition
Restore your backup
Ok, we can finally split up the bug reports between cm-10.1 and cm-10.2 which are rapidly diverging. So, what needs fixin'?
mdmower said:
Ok, we can finally split up the bug reports between cm-10.1 and cm-10.2 which are rapidly diverging. So, what needs fixin'?
Click to expand...
Click to collapse
Running 20130909... I have Interface / Signal Status Style set to text. When rebooting, a number 2147483647 appears next to the antenna for some time before changing to the number representing the db level (e.g. -81). This didn't happen with any of the CM 10.1 builds.
Is there a reason official builds aren't available right now? Link works and I see roms. Looks like there's a new one up since I flashed the test build on that page.
Edit. As far as things needing fixed, lol I honestly can't find anything major. Don't have screen flicker. Focus works on cam and video. Avrcp function works great and sends metadata to cars radio screen and the sound quality over Bluetooth is better than 10.1. Only thing that is minor is my headset button doesn't work with 10.2.
Sent from my Incredible 4G LTE using Tapatalk 2
spectre559 said:
Running 20130909... I have Interface / Signal Status Style set to text. When rebooting, a number 2147483647 appears next to the antenna for some time before changing to the number representing the db level (e.g. -81). This didn't happen with any of the CM 10.1 builds.
Click to expand...
Click to collapse
I think the radio takes a bit longer to initialize in these cm-10.2 builds, so that number is likely just whatever garbage value is in memory (or some strange initializing value) before it kicks on. I'll check to see if I can initialize the signal strength to something more meaningful, like 0db (which will affect all devices, so may take a while to get acceptance). In the meantime, I will put this in the known issues.
MJL99 said:
Is there a reason official builds aren't available right now? Link works and I see roms. Looks like there's a new one up since I flashed the test build on that page.
Click to expand...
Click to collapse
The only official cm-10.2 build available is that "experimental - nodelay" build that intervigil kicked-off when he needed feedback on whether the panel delay patches were effective and/or affecting anything else. I will try to get cm-10.2 nightlies switched on as soon as possible.
mdmower said:
The only official cm-10.2 build available is that "experimental - nodelay" build that intervigil kicked-off when he needed feedback on whether the panel delay patches were effective and/or affecting anything else. I will try to get cm-10.2 nightlies switched on as soon as possible.
Click to expand...
Click to collapse
How about the 9/8 official nightly? The file size is definitely smaller than the experimental build I noticed but newer. Also how are these builds comparable to what you have posted on goo? I see there's a 9/9 build but the file size is bigger than the most recent one on get.cm.
Sent from my Incredible 4G LTE using Tapatalk 2
MJL99 said:
How about the 9/8 official nightly?
Click to expand...
Click to collapse
No such thing... look closer. I still need to write some summary pages for some of the goo.im folders.
mdmower said:
No such thing... look closer. I still need to write some summary pages for some of the goo.im folders.
Click to expand...
Click to collapse
Doh! Took me a minute. Lol
Sent from my Incredible 4G LTE using Tapatalk 2
mdmower said:
I think the radio takes a bit longer to initialize in these cm-10.2 builds, so that number is likely just whatever garbage value is in memory (or some strange initializing value) before it kicks on. I'll check to see if I can initialize the signal strength to something more meaningful, like 0db (which will affect all devices, so may take a while to get acceptance). In the meantime, I will put this in the known issues.
Click to expand...
Click to collapse
You are right. Apparently that number corresponds to the maximum value of a 32-bit signed integer. http://en.wikipedia.org/wiki/2147483647
Ok, fireball is now on cm-10.2 nightlies.
mdmower said:
Ok, fireball is now on cm-10.2 nightlies.
Click to expand...
Click to collapse
Congrats on this. My apologies, I feel like I jumped the gun releasing the cfxe beta this morning based off of your device tree work. I foolishly misread some posts and thought fireball was on nightlies already. Otherwise I would have held off a bit longer, No disrespect was intended.
Sent from my SCH-i705 using Tapatalk 2
jrior001 said:
Congrats on this. My apologies, I feel like I jumped the gun releasing the cfxe beta this morning based off of your device tree work. I foolishly misread some posts and thought fireball was on nightlies already. Otherwise I would have held off a bit longer, No disrespect was intended.
Click to expand...
Click to collapse
Oh, no worries there. Other projects were already basing themselves on cm-10.2, I just wanted to get things in better shape before flipping the switch here (well, that and a severe lack of time to get things organized).
Installed 10.2 unofficial 9/9. Unable to change nv to ruim/SIM. Tried multiple reboots, fixing permissions, wipes. Also cannot change system select. Running on nv i constantly drop signal. Same thing happened when I tried tachyon rom. Not sure if it's a new change that happened with updates or what. Someone suggested in the tachyon thread to select options in a certain order but that didn't help either.
Sent from my Incredible 4G LTE using Tapatalk 2
MJL99 said:
Installed 10.2 unofficial 9/9. Unable to change nv to ruim/SIM. Tried multiple reboots, fixing permissions, wipes. Also cannot change system select. Running on nv i constantly drop signal. Same thing happened when I tried tachyon rom. Not sure if it's a new change that happened with updates or what. Someone suggested in the tachyon thread to select options in a certain order but that didn't help either.
Click to expand...
Click to collapse
Can you test the official 20130911 nightly? This should be included, which may help. If the problem persists, re-test in a completely clean state. Btw, fix permissions doesn't do anything helpful anymore. It was even removed from CWM.
mdmower said:
Can you test the official 20130911 nightly? This should be included, which may help. If the problem persists, re-test in a completely clean state. Btw, fix permissions doesn't do anything helpful anymore. It was even removed from CWM.
Click to expand...
Click to collapse
That worked. Initial boot from a flash over previous 10.2 build reverted to nv. Changing it and rebooting saved the settings to ruim/SIM.
Thanks for the heads up about fix permissions too.
Sent from my Incredible 4G LTE using Tapatalk 2
Camcorder feedback
Can I get some reports of audio recording in camcorder? Specifically, is there a very noticable high pitch background noise in all recordings? If you report, can you also let me know whether your panels suffers from the flicker issue (in case there's a correlation).
mdmower said:
Can I get some reports of audio recording in camcorder? Specifically, is there a very noticable high pitch background noise in all recordings? If you report, can you also let me know whether your panels suffers from the flicker issue (in case there's a correlation).
Click to expand...
Click to collapse
No high pitched noise on recordings for me on newest official nightly, 9/11. I also do not have the panel flicker.
Sent from my Incredible 4G LTE using Tapatalk 2
Hi all, I am new to the forums and I think that I need some help with a custom android project.
[Background]
I have bought a Meraki MC74, This phone is a VOIP office desk phone that has a nice 7 inch LCD screen that make for a ballin' custom intercom phone/general android device.
Cisco Meraki has dropped support for this phone, so even if I wanted to pay for a subscription, I couldn't. So custom android it is
[So what I know]
I know that the OEM OS is android 4.X.X with a custom Cisco Meraki dialer to do Meraki's cloud mumbojumbo. I was able to use ADB and Fastboot to flash ClockworkMod, and a custom version of Android 4.1.2 to get the device somewhat working. (it had lots of bugs and problems; but it was running android free of the Cisco Dialer!)
I was able to do this with the help of fellow xdadevelopers forum user "andrewmospak" (If you're reading this; I'm the dude from Ebay. And of course, thanks bro for the help so far!)
The storage is on a 4 GB Kingston EMMC.
[What I wanted for an end goal]
I wanted to have an interesting discontinued Meraki Desk phone that runs android and get all the functions of the phone working within android.
I also wanted to expand the storage from 4GB to 32GB. ( involving de-soldering existing EMMC and solder in the bigger EMMC.)
[What caused me to write this]
I would be fine if I wanted to stop there, but I wanted to try to install a GSI of android 9 in place of 4.1.2.
Again, this wouldn't be a big deal but I had to go and screw this up. I tried to resize some of the partitions (namely system to accommodate the bigger image of the android 9 GSI)but I accidentally completely killed the system,cache, and recovery partitions.
So, as one of the first steps of trouble shooting, I went to the hardest solution. The de-soldering of the EMMC.
I reached out to Andrewmospak again and asked for a full system emmc dump to try to flash his working file system to a spare 4GB EMMC to see an example of the file system of a working android EMMC. I received the image and flashed it to a spare Toshiba chip and soldered that to the phone, but I was unable to get the phone to boot into android right away, only able to load up fastboot.
Interestingly, I know that the EMMC is working because fastboot reports the S/N as the S/N of Andrewmospak's device and not the one written on my device.
[What I don't know]
Should some of the partitions on the EMMC not be recognized by Gparted in Debian? Like the User/System and others are partitioned ext4 while others are just not recognized.
Why when trying to flash partitions using Fastboot, wont fastboot recognise a recovery partition. It would just say that the partition just doesn't exist. same story with boot.
[What needs help]
I would like to know why fastboot wont see flashable volumes when using the EMMC dump flashed to another spare Toshiba EMMC, it is clearly there.
I would like to know how to reconstruct a volume to fix missing ones, and the number of partitions android needs to run.
Would I be able to flash an image of my working device to a 32gb emmc and just expand the system and user partitions into that extra space?
I will appreciate all help given to assist me and others that want a working device instead of a paperweight. ogChamp: :fingers-crossed:
That is an awesome project, and a great idea for an office line. I'll look into this!
Use MC74 for dashboard
I'm really interest to know, if you can have run a web browser on the MC74.
My needs are not fancy, I want to run a web browser on the touch screen, and have network connection with the ethernet jack in the back. I want to use it to interact with a touch dashboard for my home automation trough the webbrowser.
Thank you
Is it possible you didnt get the hidden boot partition in the emmc device? I know it isn't accessible through a sd card reader but can be seen through a SDIO controller interface.
page 15 of this document discusses this:
Google this: "us-17-Etemadieh-Hacking-Hardware-With-A-$10-SD-Card-Reader-wp.pdf" first link on blackhat.com
This project interests me as these devices are dirt cheap and i could use a few multipurpose desk phones
Thank you for starting this work. I have been waiting for this day since past couple of years now.
When you get a chance, could you please post the steps up to the point where you decided to swap the emmc?
sasha0413 said:
Hi all, I am new to the forums and I think that I need some help with a custom android project.
[Background]
I have bought a Meraki MC74, This phone is a VOIP office desk phone that has a nice 7 inch LCD screen that make for a ballin' custom intercom phone/general android device.
Cisco Meraki has dropped support for this phone, so even if I wanted to pay for a subscription, I couldn't. So custom android it is
[So what I know]
I know that the OEM OS is android 4.X.X with a custom Cisco Meraki dialer to do Meraki's cloud mumbojumbo. I was able to use ADB and Fastboot to flash ClockworkMod, and a custom version of Android 4.1.2 to get the device somewhat working. (it had lots of bugs and problems; but it was running android free of the Cisco Dialer!)
I was able to do this with the help of fellow xdadevelopers forum user "andrewmospak" (If you're reading this; I'm the dude from Ebay. And of course, thanks bro for the help so far!)
The storage is on a 4 GB Kingston EMMC.
[What I wanted for an end goal]
I wanted to have an interesting discontinued Meraki Desk phone that runs android and get all the functions of the phone working within android.
I also wanted to expand the storage from 4GB to 32GB. ( involving de-soldering existing EMMC and solder in the bigger EMMC.)
[What caused me to write this]
I would be fine if I wanted to stop there, but I wanted to try to install a GSI of android 9 in place of 4.1.2.
Again, this wouldn't be a big deal but I had to go and screw this up. I tried to resize some of the partitions (namely system to accommodate the bigger image of the android 9 GSI)but I accidentally completely killed the system,cache, and recovery partitions.
So, as one of the first steps of trouble shooting, I went to the hardest solution. The de-soldering of the EMMC.
I reached out to Andrewmospak again and asked for a full system emmc dump to try to flash his working file system to a spare 4GB EMMC to see an example of the file system of a working android EMMC. I received the image and flashed it to a spare Toshiba chip and soldered that to the phone, but I was unable to get the phone to boot into android right away, only able to load up fastboot.
Interestingly, I know that the EMMC is working because fastboot reports the S/N as the S/N of Andrewmospak's device and not the one written on my device.
[What I don't know]
Should some of the partitions on the EMMC not be recognized by Gparted in Debian? Like the User/System and others are partitioned ext4 while others are just not recognized.
Why when trying to flash partitions using Fastboot, wont fastboot recognise a recovery partition. It would just say that the partition just doesn't exist. same story with boot.
[What needs help]
I would like to know why fastboot wont see flashable volumes when using the EMMC dump flashed to another spare Toshiba EMMC, it is clearly there.
I would like to know how to reconstruct a volume to fix missing ones, and the number of partitions android needs to run.
Would I be able to flash an image of my working device to a 32gb emmc and just expand the system and user partitions into that extra space?
I will appreciate all help given to assist me and others that want a working device instead of a paperweight. ogChamp: :fingers-crossed:
Click to expand...
Click to collapse
Can't get to recovery mode -- wanna help
I'd like to help and write and app that is a (open) SIP client for the MC74. I bought an apparently new MC74 but I can't get it into recovery mode. Any help in doing this (so I can install a rooted Android)?
Holding down VolUp while connecting the POE ethernet to the WAN port doesn't work. The display remains blank then every several seconds the dislpay backlight flashes for a moment. Holding down Mute and connecting power has no effect, just boot normally to the Meraki logo screens then a minute later the normal keypad and menu display. (VolDn and powerup boots normally). I've tried this with USB flash drive (with some random recovery.img file on it) in the side USB port -- then I get an icon of a broken Android robot (presumably meaning it tried something with booting off the USB.
Has my MC74 been locked down somehow? What can I do to get a rooted Android on it?
ribo said:
I'd like to help and write and app that is a (open) SIP client for the MC74. I bought an apparently new MC74 but I can't get it into recovery mode. Any help in doing this (so I can install a rooted Android)?
Holding down VolUp while connecting the POE ethernet to the WAN port doesn't work. The display remains blank then every several seconds the dislpay backlight flashes for a moment. Holding down Mute and connecting power has no effect, just boot normally to the Meraki logo screens then a minute later the normal keypad and menu display. (VolDn and powerup boots normally). I've tried this with USB flash drive (with some random recovery.img file on it) in the side USB port -- then I get an icon of a broken Android robot (presumably meaning it tried something with booting off the USB.
Has my MC74 been locked down somehow? What can I do to get a rooted Android on it?
Click to expand...
Click to collapse
The way That I was able to boot into recovery was to hold mute and volume down NOT IMMEDIATELY hold the two only after the LCD backlight turns on. Only then you will be in recovery.
realc3blues said:
Is it possible you didnt get the hidden boot partition in the emmc device? I know it isn't accessible through a sd card reader but can be seen through a SDIO controller interface.
page 15 of this document discusses this:
Google this: "us-17-Etemadieh-Hacking-Hardware-With-A-$10-SD-Card-Reader-wp.pdf" first link on blackhat.com
This project interests me as these devices are dirt cheap and i could use a few multipurpose desk phones
Click to expand...
Click to collapse
My linux machine recognizes the mystery partitions but not their contents or partition scheme with some cheap USB to SD adapters. I think it works well. Thanks for the recommendation though!
ribo said:
I'd like to help and write and app that is a (open) SIP client for the MC74. I bought an apparently new MC74 but I can't get it into recovery mode. Any help in doing this (so I can install a rooted Android)?
Holding down VolUp while connecting the POE ethernet to the WAN port doesn't work. The display remains blank then every several seconds the dislpay backlight flashes for a moment. Holding down Mute and connecting power has no effect, just boot normally to the Meraki logo screens then a minute later the normal keypad and menu display. (VolDn and powerup boots normally). I've tried this with USB flash drive (with some random recovery.img file on it) in the side USB port -- then I get an icon of a broken Android robot (presumably meaning it tried something with booting off the USB.
Has my MC74 been locked down somehow? What can I do to get a rooted Android on it?
Click to expand...
Click to collapse
You need to hold down the VOLUME DOWN button before powering on the unit, and then continue to hold it. The phone will go into Fastboot mode. The screen will be blank, but backlit, and usually the LED lights up red. Here, you can flash a custom recovery firmware image (such as the ClockworkMod one that's floating around) that allows you to make changes to the system and user partitions. The thing you're seeing with the Android robot is expected. That's the default recovery firmware. Once you flash custom recovery firmware in Fastboot mode, you then unplug the unit, hold down the MUTE button, plug the device in, and continue to hold the MUTE button. It may take some time for it to get into the recovery firmware, but be patient. FYI, VOLUME UP is used for that feature where you can switch between two "slots" for firmware. I don't really know what that is, but I know that it's a thing with Android. It's pretty much unused on the MC as far as I can tell.
Has anyone considered working backwards with the version of Android running on the MC, rather than installing an entirely new version? So, instead of trying to get new firmware to work on the unit, why not work with whatever's on the device by default and pull out what you don't need? I know that some people have gotten different versions of Android to work on the unit, but this leads to bugs or hiccups. I'd imagine that this is because the kernel for that firmware isn't specifically made for the MC, but don't take my word for it. That's just a guess.
Due to the current pandemic situation that's going on here, I've decided to occupy my time by examining the MC in depth. I've managed to get ADB shell working when the device has booted normally, allowing me to examine the filesystem and pull out whatever Meraki included with the firmware. Even got the rainbow LED to stop obnoxiously glowing! I'm currently working on getting the system UI to work (there's no status bar or app switcher).
Got adbd running on MC74, Sort of got Linphone going
@sasha0413 and @jazzcandle, I got the boot.img updated so I could set 'ro.secure=0' in /default.prop in the boot up ramdisk. So now I can 'adb' into it by TCP or USB. Thanks for the help. (My MC74 calls itself a 'test-phone' so it may be a little different software. The problem was that the 'recovery' mode installed on it was pretty subtle, nothing showed on the screen.
My MC74 runs '4.2.5-meraki' version of JellyBean api 17, because I'm not good at porting newer versions of Android -- and because there may be modifications / drivers that Meraki put in to support the hardware, I'm working on a phone app with the original JellyBean.
I managed to get an old version of 'linphone' working to the extent that I can make a call -- and can be heard -- but I haven't mastered the speakers (Android AudioManager/MediaPlayer, etc) so I can't hear the phone call. I can play audio speakerphone speaker, but can't play it on the handset speaker. Figuring out the Android Audio system for JellyBean is hard, the implementation has change a lot since then.
---------- Post added at 14:11 ---------- Previous post was at 14:04 ----------
[/COLOR @jazzcandle I installed com.teslacoilsw.launcher-4.1.0-41000-minAPI16.apk as a launcher and told use it as the launcher rather than /data/app/com.meraki.dialer2-1.apk
How did you stop the RGB LED from cycling through the colors? Does something like: /system/app/DroidNode.apk or /system/app/DroidNodeSystemSvcs.apk start the led cycling, then perahps com.meraki.dialer2 stop it -- when it initializes?
ribo said:
My MC74 calls itself a 'test-phone' so it may be a little different software. The problem was that the 'recovery' mode installed on it was pretty subtle, nothing showed on the screen.
Click to expand...
Click to collapse
This is something that stumped me early on as well. But have no fear, all MCs run the same firmware, and you're not running different "test" firmware. The "test phone" value you're referring to is only seen in the recovery partition in the "default.prop" file, where "ro.product.model" is set to "BCM28155_TEST_PHONE". When booting normally, this value is set to "Meraki MC74" instead.
ribo said:
I managed to get an old version of 'linphone' working to the extent that I can make a call -- and can be heard -- but I haven't mastered the speakers (Android AudioManager/MediaPlayer, etc) so I can't hear the phone call. I can play audio speakerphone speaker, but can't play it on the handset speaker. Figuring out the Android Audio system for JellyBean is hard, the implementation has change a lot since then.
Click to expand...
Click to collapse
The way audio output works on the MC is a bit strange. In fact, it's not really Android's fault from what I can tell. However, I found that you have to "poke" the audio HAL to get it functioning somewhat normally (ie. getting audio to actually play through the speakers). You can do this by running the following command in the shell:
$ tinymix 1 1
At this point, you should be able to hear audio output through the speakers. Additionally, you should be able to switch between handset and speakerphone mode (so long as the app you're using allows you to do this).
ribo said:
I installed com.teslacoilsw.launcher-4.1.0-41000-minAPI16.apk as a launcher and told use it as the launcher rather than /data/app/com.meraki.dialer2-1.apk
Click to expand...
Click to collapse
You should delete the Dialer apk, you don't need it. In fact, you should delete the DroidNode.apk and DroidNodeSystemSvcs.apk files as well.
ribo said:
How did you stop the RGB LED from cycling through the colors? Does something like: /system/app/DroidNode.apk or /system/app/DroidNodeSystemSvcs.apk start the led cycling, then perahps com.meraki.dialer2 stop it -- when it initializes?
Click to expand...
Click to collapse
You need to modify "init.bcm911130_me1.rc" within "boot.img" and either remove or comment out the following:
Code:
service lightsd /system/bin/lightsd
class main
socket lightsd stream 600 system system
user root
Controlling RGB LED on MC74
Thanks jazzcandle, I'll look into /system/bin/lightsd to see what it does.
lightsd seems to open ANDROID_SOCKET_lightsd and listen to /dev/socket/lightsd
It seems to directly write to these /sys files to change the LEDs through which must be controlled through the SOC's GPIO pins..
/sys/class/leds/red/brightness
/sys/class/leds/green/brightness
/sys/class/leds/blue/brightness
/sys/class/leds/white/delay_off
/sys/class/leds/white/brightness
/sys/class/gpio/export
/sys/class/gpio/gpio11/directionout
/sys/class/gpio/gpio11/value
am broadcast -a com.meraki.LIGHTSD_START
I would be great to know what all the GPIO devices did and their a addresses.
I've left the Dialer2, DroidNode and DroidNodeSystemSvcs apps running at this point to see what they do and how they are used. I agree that eventually they need to be removed because they connect to cisco/meraki web services when they start up.
I noticed that the com.meraki.dialer2.LEDController class is how the dialer controls the LEDs:
public void notifyLeds(LedMode mode, int red, int green, int blue) {
this.r = red;
this.g = green;
this.b = blue;
this.m = mode;
sendLightCommand();
}
class LightCmd implements Consumer {
public void accept(Object o) {
Intent i = (Intent)o;
i.putExtra("red", r);
i.putExtra("green", g);
i.putExtra("blue", b);
Log.i(TAG, String.format("Broadcasting color change to rgb(%d, %d, %d)",
new Object[]{r, Integer.valueOf(g), Integer.valueOf(b)}));
ctx.sendBroadcast(i);
}
}
private void sendLightCommand() {
Consumer cons = new LightCmd();
getIntent().ifPresent(cons);
}
Click to expand...
Click to collapse
Methods ilke 'notifyLeds' takes a mode (Solid, Pulse, or Rainbow) and the R, G, B values and uses the sendLightCommand() method which broadcasts an intent that will probably be handled by something like the /system/bin/lightsd daemon. (I'm trying to document all these things for customizing/developing a SIP app.
I notice that the MC74 app is built on the PJSIP ( org.pjsip.pjua2 package) I was thinking of use the org.linphone SIP package. Anyone have experience with these SIP packages?
ribo said:
(I'm trying to document all these things for customizing/developing a SIP app.
I notice that the MC74 app is built on the PJSIP ( org.pjsip.pjua2 package) I was thinking of use the org.linphone SIP package. Anyone have experience with these SIP packages?
Click to expand...
Click to collapse
Thanks for documenting this, this is awesome info. A while back I built a rudimentary SIP client for MC74 based on the AJVoIP SIP package. I gave up on it once my trial period for that package expired. It was quirky, with flaky audio and no LED control (which both now could be solved by the info in this thread), but I did have hookswitch (hangup/answer by picking up the handset) working.
In the spirit of documentation, the hookswitch is an ambient light sensor that gets covered or uncovered by the handset's earpiece. The original Dialer2 app reads the raw value and compares it to a calibrated set point to determine on/off hook state. Reading the path
Code:
/sys/devices/virtual/input/input0/event0/device/raw_adc
with a FileReader will get you the current value. For my device, off hook (answered) is a value below 110. On hook (hung up) is a value above 110. For my testing I just polled this file every 250ms but you could attach a FileObserver to it or something.
jazzcandle said:
Has anyone considered working backwards with the version of Android running on the MC, rather than installing an entirely new version? So, instead of trying to get new firmware to work on the unit, why not work with whatever's on the device by default and pull out what you don't need?
Click to expand...
Click to collapse
This is actually what I am working on with a unit that I got.
The phone I have (from the build.prop file):
Code:
ro.build.version.release=4.2.3-phone-5068355-southern-userdebug
ro.product.model=Meraki MC 74
ro.product.brand=Meraki
ro.product.name=capri_me1
ro.product.device=capri_me1
ro.product.board=capri
Currently trying to work on getting ADB working from within the phone and not just within the Clockwork recovery that I got loaded on it.
Getting a pretty close stock experience on the MC74 is totally possible with some dedication and work. For reasons I cant get into, I am unable to provide the steps / files that it took to get where I am, but I have a functional MC74 with working handset & speakerphone. The only next thing I need to work on is getting the "IR" sensor to hangup in specific Dialer applications.
https://imgur.com/a/FFVq1sL
I am using Grandstream Softphone dialer.
drraccoon said:
Getting a pretty close stock experience on the MC74 is totally possible with some dedication and work. For reasons I cant get into, I am unable to provide the steps / files that it took to get where I am, but I have a functional MC74 with working handset & speakerphone. The only next thing I need to work on is getting the "IR" sensor to hangup in specific Dialer applications.
Click to expand...
Click to collapse
I was able to achieve the same, except GS dialer is not scaled correctly.
Not able to post link to image, as I don't have 10 messages.
So it is a/6aQYsz6 on imgur
Did not bother to fix it, as my intent is custom PJSIP dialer (someday
Headset sensor, led, mixer - figured out.
The only mystery is "mute" button and the red LED behind it.
sasha0413 said:
Hi all, I am new to the forums and I think that I need some help with a custom android project.
[Background]
I have bought a Meraki MC74, This phone is a VOIP office desk phone that has a nice 7 inch LCD screen that make for a ballin' custom intercom phone/general android device.
Cisco Meraki has dropped support for this phone, so even if I wanted to pay for a subscription, I couldn't. So custom android it is
[So what I know]
I know that the OEM OS is android 4.X.X with a custom Cisco Meraki dialer to do Meraki's cloud mumbojumbo. I was able to use ADB and Fastboot to flash ClockworkMod, and a custom version of Android 4.1.2 to get the device somewhat working. (it had lots of bugs and problems; but it was running android free of the Cisco Dialer!)
I was able to do this with the help of fellow xdadevelopers forum user "andrewmospak" (If you're reading this; I'm the dude from Ebay. And of course, thanks bro for the help so far!)
The storage is on a 4 GB Kingston EMMC.
[What I wanted for an end goal]
I wanted to have an interesting discontinued Meraki Desk phone that runs android and get all the functions of the phone working within android.
I also wanted to expand the storage from 4GB to 32GB. ( involving de-soldering existing EMMC and solder in the bigger EMMC.)
[What caused me to write this]
I would be fine if I wanted to stop there, but I wanted to try to install a GSI of android 9 in place of 4.1.2.
Again, this wouldn't be a big deal but I had to go and screw this up. I tried to resize some of the partitions (namely system to accommodate the bigger image of the android 9 GSI)but I accidentally completely killed the system,cache, and recovery partitions.
So, as one of the first steps of trouble shooting, I went to the hardest solution. The de-soldering of the EMMC.
I reached out to Andrewmospak again and asked for a full system emmc dump to try to flash his working file system to a spare 4GB EMMC to see an example of the file system of a working android EMMC. I received the image and flashed it to a spare Toshiba chip and soldered that to the phone, but I was unable to get the phone to boot into android right away, only able to load up fastboot.
Interestingly, I know that the EMMC is working because fastboot reports the S/N as the S/N of Andrewmospak's device and not the one written on my device.
[What I don't know]
Should some of the partitions on the EMMC not be recognized by Gparted in Debian? Like the User/System and others are partitioned ext4 while others are just not recognized.
Why when trying to flash partitions using Fastboot, wont fastboot recognise a recovery partition. It would just say that the partition just doesn't exist. same story with boot.
[What needs help]
I would like to know why fastboot wont see flashable volumes when using the EMMC dump flashed to another spare Toshiba EMMC, it is clearly there.
I would like to know how to reconstruct a volume to fix missing ones, and the number of partitions android needs to run.
Would I be able to flash an image of my working device to a 32gb emmc and just expand the system and user partitions into that extra space?
I will appreciate all help given to assist me and others that want a working device instead of a paperweight. ogChamp: :fingers-crossed:
Click to expand...
Click to collapse
Hey, I am interested but I don't have the device.
First of all:
I would be fine if I wanted to stop there, but I wanted to try to install a GSI of android 9 in place of 4.1.2.
Click to expand...
Click to collapse
You can install a GSI on a 4.1.2 based device, but you can't without creating a vendor partition, GSI is a part of the Project Treble released with Oreo. It requires a vendor partition to work. On 4.1.2, there's simply no device with a partition called vendor, so you can't flash a GSI.
But, if you have a fully working Android Pie tree, you can make a vendor partition yourself.
alex39wkd said:
I was able to achieve the same, except GS dialer is not scaled correctly.
Not able to post link to image, as I don't have 10 messages.
So it is a/6aQYsz6 on imgur
Did not bother to fix it, as my intent is custom PJSIP dialer (someday
Headset sensor, led, mixer - figured out.
The only mystery is "mute" button and the red LED behind it.
Click to expand...
Click to collapse
As you didn't mention that you couldn't share any information like the reply previous to yours, would it be possible for you to share what you used to get there?
As someone with only linux, networking and voip knowledge and that never played around with Android ROMs/ADB before, that would get me started as I can ATM only get to ADB.
Also, did you use the version of android already on the Phone or Flashed it with a new ROM?
Thank you!
jtthecanadian said:
As you didn't mention that you couldn't share any information like the reply previous to yours, would it be possible for you to share what you used to get there?
As someone with only linux, networking and voip knowledge and that never played around with Android ROMs/ADB before, that would get me started as I can ATM only get to ADB.
Also, did you use the version of android already on the Phone or Flashed it with a new ROM?
Thank you!
Click to expand...
Click to collapse
I have used "adb pull" (in recovery mode) to dump boot partition, just used path to it in /dev/...
Used android tools to decompress and unpack boot.
Changed ro.secure to 0 and something like "meraki usb debug" to 1
Repacked boot partition
Used adb to switch to fastboot
Flashed boot and boot2 with this image
Now it is accessable as normal Android phone, for whatever you might want to do with it.
Is anyone able to provide a working ROM for this device? I'm extremely confused about how to get this working. I would greatly appreciate any advice.